Triple
T14350575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sour Soul |
E355839
|
entity |
| Predicate | featuresLiveInstrumentation |
P113893
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Sour Soul, featuresLiveInstrumentation, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresLiveInstrumentation Context triple: [Sour Soul, featuresLiveInstrumentation, true]
-
A.
coreInstrument
Indicates that an instrument plays a central or primary role in performing an action or achieving an outcome.
-
B.
typicalInstrumentation
Indicates the usual or standard set of instruments commonly associated with performing or realizing something (such as a work, genre, or piece).
-
C.
enablingInstrument
Indicates that one entity serves as the means, tool, or instrument that enables another entity’s action or effect to occur.
-
D.
featuresRhythm
Indicates that something includes, exhibits, or is characterized by a particular rhythmic pattern or structure.
-
E.
supportsDynamicInstrumentation
Indicates that an entity is capable of being instrumented or monitored at runtime without requiring recompilation or restart.
- 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_69d82790a7e08190877e2d349b2e8d8e |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de8f4e1e588190bdc7aaf7a2819948 |
completed | April 14, 2026, 7:02 p.m. |
| PD | Predicate disambiguation | batch_69de2a9958e881909d03ac03f135163e |
completed | April 14, 2026, 11:52 a.m. |
| PDg | Predicate description generation | batch_69de2e8a40e4819080240c874da1842c |
completed | April 14, 2026, 12:09 p.m. |
Created at: April 10, 2026, 1:14 a.m.