Triple
T22486645
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tall Boy |
E555900
|
entity |
| Predicate | liveArrangementFeatures |
P48738
|
FINISHED |
| Object | extended jams |
—
|
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: extended jams | Statement: [Tall Boy, liveArrangementFeatures, extended jams]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: liveArrangementFeatures Context triple: [Tall Boy, liveArrangementFeatures, extended jams]
-
A.
arrangementFeatures
Indicates that one entity specifies or characterizes the structural or compositional features of an arrangement involving another entity.
-
B.
hasArrangementFeature
Indicates that one entity possesses a specific structural or spatial arrangement characteristic related to another entity or context.
-
C.
hasLiveArrangement
Indicates that there is an active, ongoing arrangement or agreement currently in effect between the related entities.
-
D.
livePerformanceFeature
chosen
Indicates that one entity is included or highlighted as a component of another entity’s live performance.
-
E.
featuresArrangementBy
Indicates that one entity determines or specifies the spatial or structural arrangement of features in another entity.
- 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_69f15c3da9588190abf2f96d3104edfb |
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.