Triple
T8620130
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yavin 4 |
E204141
|
entity |
| Predicate | celebrationEvent |
P24712
|
FINISHED |
| Object | medal ceremony after Battle of Yavin |
—
|
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: medal ceremony after Battle of Yavin | Statement: [Yavin 4, celebrationEvent, medal ceremony after Battle of Yavin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: celebrationEvent Context triple: [Yavin 4, celebrationEvent, medal ceremony after Battle of Yavin]
-
A.
celebratedEvent
Indicates that an entity has been honored, commemorated, or festively observed as a special event.
-
B.
publicCelebration
Indicates a relationship where an event, achievement, or occasion is celebrated openly and collectively in a public setting.
-
C.
eveCelebrationOn
Indicates that an event or entity is engaged in or associated with a celebration occurring on a specific date or occasion.
-
D.
celebrationName
chosen
Indicates the specific name or title assigned to a celebration or festive event.
-
E.
isCelebratoryOf
Indicates that something expresses celebration, honor, or festive recognition directed toward a particular event, person, or occasion.
- 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_69ca832ceab8819096e4a9f546695079 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cc471458f48190a6d8858f8074727d |
completed | March 31, 2026, 10:13 p.m. |
| PD | Predicate disambiguation | batch_69cc455437488190b7506f820daf6e32 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:26 p.m.