Triple
T11063217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Disney on Broadway Concert Series |
E261558
|
entity |
| Predicate | live |
P37189
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Disney on Broadway Concert Series, live, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: live Context triple: [Disney on Broadway Concert Series, live, true]
-
A.
living
Indicates that an entity is alive or currently exists in a living state.
-
B.
recordedAsLive
chosen
Indicates that an audio or video performance was captured in real time before an audience or in a live setting, rather than produced or edited in a studio environment.
-
C.
alsoLiveOn
Indicates that two or more entities reside or are located on the same place, platform, medium, or environment.
-
D.
liveAction
Indicates that an entity is a live-action (non-animated) adaptation, portrayal, or version of another entity.
-
E.
notableLiveRecording
Indicates that there exists a particularly significant or well-known live recording associated with the subject.
- 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_69d6aa98650481908609c7c56bfa7902 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d798ed07f88190bf501d9f63386ada |
completed | April 9, 2026, 12:17 p.m. |
| PD | Predicate disambiguation | batch_69d74411d9e881908c0eeafa0f38e4b6 |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:26 p.m.