Triple
T26998017
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Icelandic National Day |
E680027
|
entity |
| Predicate | reasonForDateChoice |
P86419
|
FINISHED |
| Object | birthday of Jón Sigurðsson |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: birthday of Jón Sigurðsson | Statement: [Icelandic National Day, reasonForDateChoice, birthday of Jón Sigurðsson]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForDateChoice Context triple: [Icelandic National Day, reasonForDateChoice, birthday of Jón Sigurðsson]
-
A.
reasonForTime
Indicates that one entity provides the explanation or cause for a particular point or duration of time associated with another entity.
-
B.
selectionReason
Indicates the reason or justification for choosing or selecting one entity over alternatives.
-
C.
reasonForHoliday
chosen
Indicates the underlying cause, purpose, or occasion for which a holiday is observed.
-
D.
reasonForUse
Indicates that one entity specifies the justification, purpose, or motivation for using another entity.
-
E.
reasonForChange
Indicates that one entity serves as the cause, justification, or motivation for a modification or change in another entity or state.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69eeeb52908c8190bd246244686aa455 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f6d6a6b04c8190bee4cf9c00665ef7 |
completed | May 3, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69f6d26ceb08819091c71c001e954936 |
completed | May 3, 2026, 4:43 a.m. |
Created at: April 27, 2026, 6:55 a.m.