Triple
T22485268
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A Live One |
E555860
|
entity |
| Predicate | originalMaterialFrom |
P49659
|
FINISHED |
| Object | multiple concert venues |
—
|
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: multiple concert venues | Statement: [A Live One, originalMaterialFrom, multiple concert venues]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalMaterialFrom Context triple: [A Live One, originalMaterialFrom, multiple concert venues]
-
A.
originalMaterialFor
Indicates that one entity serves as the source or basis material from which another entity is derived, adapted, or created.
-
B.
originalMaterialRecorded
Indicates that a recording was made directly from the original material, rather than from a copy or derivative source.
-
C.
featuresMaterialFrom
chosen
Indicates that one entity incorporates, contains, or is composed of material originating from another entity.
-
D.
materialSource
Indicates that one entity serves as the origin or provider of the material or substance used by another entity.
-
E.
sourceMaterialType
Indicates the type or category of material from which something originates or is derived.
- 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_69e11e53897c819088863779f8c50bb0 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15c3bb8cc8190950efd84ebe86b73 |
completed | April 29, 2026, 1:17 a.m. |
| PD | Predicate disambiguation | batch_69e898b6eee08190ba673a0ee329e671 |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:49 p.m.