Triple
T2664219
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Annie Savoy |
E55594
|
entity |
| Predicate | annualRitual |
P7073
|
FINISHED |
| Object | chooses one player each season to mentor |
—
|
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: chooses one player each season to mentor | Statement: [Annie Savoy, annualRitual, chooses one player each season to mentor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: annualRitual Context triple: [Annie Savoy, annualRitual, chooses one player each season to mentor]
-
A.
ritualDate
Indicates the specific date on which a ritual or ceremonial event takes place.
-
B.
annualEvent
chosen
Indicates that an event occurs once every year on a recurring basis.
-
C.
hasRitualCalendar
Indicates that an entity maintains or is associated with a structured schedule of ritual or ceremonial events.
-
D.
ritualStructure
Indicates a relationship where an entity is a structure or built feature specifically used for performing rituals or ceremonial practices.
-
E.
ritualPurpose
Indicates the intended function, goal, or role that a ritual is meant to serve or fulfill.
- 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_69ab49e54de48190be708cd1cf8be073 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd96dba44819085c3e651afba7806 |
completed | March 7, 2026, 7:53 a.m. |
| PD | Predicate disambiguation | batch_69abd81768748190bd965f367cf6ef37 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:54 p.m.