Triple
T1901581
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zadok the Priest |
E37699
|
entity |
| Predicate | traditionallyPerformedAt |
P17057
|
FINISHED |
| Object | anointing of the sovereign |
—
|
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: anointing of the sovereign | Statement: [Zadok the Priest, traditionallyPerformedAt, anointing of the sovereign]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionallyPerformedAt Context triple: [Zadok the Priest, traditionallyPerformedAt, anointing of the sovereign]
-
A.
celebratedDuring
Indicates that an event, tradition, or activity takes place or is observed within the time span of a specified celebration or festive period.
-
B.
festivalHeldIn
Indicates that a festival takes place or is hosted at a specific location or venue.
-
C.
performsMusicIn
Indicates that an entity presents or plays music within a particular venue, event, or context.
-
D.
typicallyHeldIn
chosen
Indicates that an event, activity, or process most commonly or usually takes place within a particular location, venue, or context.
-
E.
isCelebratedIn
Indicates that an event, person, or occasion is honored, observed, or commemorated within a particular place, time, or context.
- 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_69a8861be7148190a680937ec451a304 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb34d94fc8190a5bf1e582c77c725 |
completed | March 7, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69abafe9f8b0819086d8f6288511c66d |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:35 p.m.