Triple
T27050965
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | YouTube Symphony Orchestra |
E684770
|
entity |
| Predicate | locationOfSecondMajorEvent |
P116861
|
FINISHED |
| Object | Sydney Opera House |
—
|
NE NERFINISHED |
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: Sydney Opera House | Statement: [YouTube Symphony Orchestra, locationOfSecondMajorEvent, Sydney Opera House]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationOfSecondMajorEvent Context triple: [YouTube Symphony Orchestra, locationOfSecondMajorEvent, Sydney Opera House]
-
A.
cityOfSecondMajorEvent
Indicates the city where the second major event in a sequence or series takes place.
-
B.
secondEventLocation
chosen
Indicates the location where the second event in a sequence takes place.
-
C.
secondOldestEvent
Indicates that an event is the second most ancient or earliest in time within a specified set or sequence of events.
-
D.
secondMajorEarthquakeDate
Indicates the calendar date on which the second major earthquake in a specified sequence or context occurred.
-
E.
significantEventPlace
Indicates the place where a significant event occurred or is associated with an entity.
- 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_69ef14829fac8190914bef9ecc3005d7 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69fe766490c081908c49c8cc07d0ae9b |
completed | May 8, 2026, 11:48 p.m. |
| PD | Predicate disambiguation | batch_69fe75bb5f4481908572a5ffcbdc5154 |
completed | May 8, 2026, 11:46 p.m. |
Created at: April 27, 2026, 8:14 a.m.