Triple
T30361163
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Promise box set |
E772289
|
entity |
| Predicate | containsLivePerformance |
P197891
|
FINISHED |
| Object | Houston 1978 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: Houston 1978 concert | Statement: [The Promise box set, containsLivePerformance, Houston 1978 concert]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsLivePerformance Context triple: [The Promise box set, containsLivePerformance, Houston 1978 concert]
-
A.
hasLivePerformanceWith
Indicates that two or more entities participate together in the same live performance event.
-
B.
hasLivePerformanceComponent
chosen
Indicates that something includes or involves a live performance as a significant component or feature.
-
C.
hasLivePerformanceStatus
Indicates whether an entity’s live performance is occurring, scheduled, completed, or otherwise characterized by a specific performance status.
-
D.
hasLivePerformanceSetting
Indicates that an entity is associated with a particular context or environment in which a live performance takes place.
-
E.
hasLivePerformanceStyle
Indicates that an entity is associated with a particular style or manner of live performance.
- 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_69f2248c6f5c8190a6177842bf791a3c |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fef8c3f2388190b995ec173512945a |
completed | May 9, 2026, 9:05 a.m. |
| PD | Predicate disambiguation | batch_69fef65975608190960b78d27e806d4f |
completed | May 9, 2026, 8:54 a.m. |
Created at: April 29, 2026, 7:58 p.m.