Triple
T36736448
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coronation Choir |
E907490
|
entity |
| Predicate | eventTypePerformedAt |
P187016
|
FINISHED |
| Object | royal coronation concert |
—
|
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: royal coronation concert | Statement: [Coronation Choir, eventTypePerformedAt, royal coronation concert]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eventTypePerformedAt Context triple: [Coronation Choir, eventTypePerformedAt, royal coronation concert]
-
A.
eventOccurredAt
Indicates that a particular event took place at a specific time or location.
-
B.
wasPerformedAt
Indicates that an action or event took place at a specific location or venue.
-
C.
occurredDuring
Indicates that one event or action took place within the temporal span of another event or time period.
-
D.
presentedAtTime
Indicates that an event, action, or item was presented or occurred at a specific point in time.
-
E.
eventDateContext
Indicates the contextual role or significance that a specific date has within an event (e.g., whether it is the start, end, deadline, or another relevant temporal marker).
- F. None of above. chosen
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_69f76e75aa6881909b844d00a3888ee5 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb2e940d5c8190bceae77daf4ef512 |
completed | May 6, 2026, 12:05 p.m. |
| PD | Predicate disambiguation | batch_69f9fec70bd881909c658a3c5020318b |
completed | May 5, 2026, 2:29 p.m. |
| PDg | Predicate description generation | batch_69fb2e9309fc81909dfefd9020d6fbad |
completed | May 6, 2026, 12:05 p.m. |
Created at: May 3, 2026, 4:12 p.m.