Triple
T27051060
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | YouTube Symphony Orchestra 2009 project |
E684773
|
entity |
| Predicate | locationOfFinalEvent |
P12513
|
FINISHED |
| Object | Carnegie Hall |
—
|
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: Carnegie Hall | Statement: [YouTube Symphony Orchestra 2009 project, locationOfFinalEvent, Carnegie Hall]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationOfFinalEvent Context triple: [YouTube Symphony Orchestra 2009 project, locationOfFinalEvent, Carnegie Hall]
-
A.
locationOfEventDescribed
Indicates that one entity is the place or setting where the event described by another entity occurs.
-
B.
formerFinishLocation
Indicates that an entity was previously the finish location of an event or activity, but no longer holds that status.
-
C.
finalsLocation
chosen
Indicates the place where the final stage or concluding event of something (such as a competition or process) takes place.
-
D.
eventConcludedAtLocation
Indicates that an event has finished or come to an end at a specific location.
-
E.
lastLocation
Indicates the most recent known place or position where an entity was located.
- 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_69fe779248c081909f0ed1a2a0df23db |
completed | May 8, 2026, 11:53 p.m. |
| PD | Predicate disambiguation | batch_69fe76eaf6d48190998bc7168749cc42 |
completed | May 8, 2026, 11:51 p.m. |
Created at: April 27, 2026, 8:14 a.m.