Triple
T29585452
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Meskerem |
E753706
|
entity |
| Predicate | associatedWithNewYear |
P51416
|
FINISHED |
| Object | Enkutatash |
E206768
|
NE 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: Enkutatash | Statement: [Meskerem, associatedWithNewYear, Enkutatash]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithNewYear Context triple: [Meskerem, associatedWithNewYear, Enkutatash]
-
A.
newYearCoincidesWith
Indicates that the occurrence of a new year happens at the same time as another specified event or time period.
-
B.
traditionalNewYearType
Indicates that an entity is associated with a specific type or category of traditional New Year celebration.
-
C.
newYearOccursIn
chosen
Indicates that the celebration or observance of New Year takes place within a specified temporal or calendrical context (such as a particular month, season, or year).
-
D.
isAmongFirstToSeeNewYear
Indicates that an entity experiences or observes the arrival of the New Year earlier than most others.
-
E.
associatedWithAnniversary
Indicates a relationship where something is connected or related to an anniversary event, date, or celebration.
- F. None of above.
Provenance (4 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_69f0ef80bf8c8190ad286e99f7df0c63 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a26e5d6b8d88190975bf0683d7b9b7f |
completed | June 8, 2026, 3:55 p.m. |
| PD | Predicate disambiguation | batch_6a0379e0f3d88190a4ee7b0673f1ef90 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 28, 2026, 6:10 p.m.