Triple
T27051071
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | YouTube Symphony Orchestra 2009 project |
E684773
|
entity |
| Predicate | finalEventDate |
P140
|
FINISHED |
| Object | 2009-04-15 |
—
|
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: 2009-04-15 | Statement: [YouTube Symphony Orchestra 2009 project, finalEventDate, 2009-04-15]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalEventDate Context triple: [YouTube Symphony Orchestra 2009 project, finalEventDate, 2009-04-15]
-
A.
finalShowDate
Indicates the date on which a show, series, or performance has its last scheduled or final airing or presentation.
-
B.
finalRoundDate
Indicates the date on which the final round of an event, process, or competition takes place.
-
C.
finalShutdownDate
Indicates the date on which an entity is permanently shut down or ceases operation.
-
D.
endDate
chosen
Indicates the point in time at which an event, state, or relationship stops being valid or comes to a conclusion.
-
E.
finalBoutDate
Indicates the date on which the last or final bout (e.g., match or contest) took place.
- 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_69f71f8ee0688190bd025f27993452d3 |
completed | May 3, 2026, 10:12 a.m. |
| PD | Predicate disambiguation | batch_69f71cc405c08190863565609a4c8499 |
completed | May 3, 2026, 10 a.m. |
Created at: April 27, 2026, 8:14 a.m.