Triple
T4005514
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Symphony No. 4 (Harbison) |
E89515
|
entity |
| Predicate | hasInstrumentationDetail |
P1149
|
FINISHED |
| Object | unknown |
—
|
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: unknown | Statement: [Symphony No. 4 (Harbison), hasInstrumentationDetail, unknown]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInstrumentationDetail Context triple: [Symphony No. 4 (Harbison), hasInstrumentationDetail, unknown]
-
A.
containsInstrumentWithStatus
Indicates that an entity includes or is associated with an instrument that has a specified status.
-
B.
supportsDynamicInstrumentation
Indicates that an entity is capable of being instrumented or monitored at runtime without requiring recompilation or restart.
-
C.
typicalInstrumentation
chosen
Indicates the usual or standard set of instruments commonly associated with performing or realizing something (such as a work, genre, or piece).
-
D.
hasImplementationDetail
Indicates that one entity specifies or contains a concrete implementation detail or internal mechanism related to another entity.
-
E.
usesInstrument
Indicates that an agent performs an action by employing a specific instrument or tool as the means to carry it out.
- 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_69aed9585e788190bec2d39deba3750f |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefa8579288190940487ad07e38de0 |
completed | March 9, 2026, 4:51 p.m. |
| PD | Predicate disambiguation | batch_69aef8f89f2881909b0965419d15d46c |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:34 p.m.