Triple
T27048307
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ummagumma |
E684698
|
entity |
| Predicate | hasLiveComponent |
P80816
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Ummagumma, hasLiveComponent, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLiveComponent Context triple: [Ummagumma, hasLiveComponent, yes]
-
A.
hasLivingComponents
chosen
Indicates that an entity includes or is composed of one or more living or biological components.
-
B.
hasComponentCurrent
Indicates that an entity currently includes or contains a specific component as part of its present composition or structure.
-
C.
hasLiveSource
Indicates that an entity is connected to or derived from a real-time, continuously updating data or content source.
-
D.
hasLiveShowElement
Indicates that something includes or is associated with a component or feature of a live show or live performance.
-
E.
hasLiveUse
Indicates that something is currently being used or actively in operation in a live, real-world context.
- 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_69ef148193c48190bb1a0cfae6a407c4 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f7308a096081909d66a56f3c926806 |
completed | May 3, 2026, 11:24 a.m. |
| PD | Predicate disambiguation | batch_69f72a00c5f081908b6539d15baf4e12 |
completed | May 3, 2026, 10:57 a.m. |
Created at: April 27, 2026, 8:12 a.m.