Triple
T27816568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bleachers |
E702686
|
entity |
| Predicate | hasLiveConfiguration |
P181735
|
FINISHED |
| Object | touring band backing Jack Antonoff |
—
|
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: touring band backing Jack Antonoff | Statement: [Bleachers, hasLiveConfiguration, touring band backing Jack Antonoff]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLiveConfiguration Context triple: [Bleachers, hasLiveConfiguration, touring band backing Jack Antonoff]
-
A.
hasConfiguration
Indicates that an entity is associated with or defined by a particular configuration or setup.
-
B.
hasConfigurationFile
Indicates that an entity is associated with or defined by a specific configuration file.
-
C.
hasLiveSource
Indicates that an entity is connected to or derived from a real-time, continuously updating data or content source.
-
D.
hasLivingComponents
Indicates that an entity includes or is composed of one or more living or biological components.
-
E.
hasLiveActionVersion
Indicates that an entity has a corresponding adaptation or version produced in live-action (with real actors and physical settings) rather than animation or other non-live formats.
- F. None of above. chosen
Provenance (4 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_69ef840a16748190926719ab96120bae |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f7824dc3f0819092a5102895b4a478 |
completed | May 3, 2026, 5:13 p.m. |
| PD | Predicate disambiguation | batch_69f780fc5ed88190b7200ee5a29940af |
completed | May 3, 2026, 5:08 p.m. |
| PDg | Predicate description generation | batch_69f7817c79e081908e685c48165e086b |
completed | May 3, 2026, 5:10 p.m. |
Created at: April 27, 2026, 5:45 p.m.