Triple
T7102889
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Improvisation 11 |
E165501
|
entity |
| Predicate | compositionFeatures |
P33619
|
FINISHED |
| Object | dynamic lines |
—
|
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: dynamic lines | Statement: [Improvisation 11, compositionFeatures, dynamic lines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: compositionFeatures Context triple: [Improvisation 11, compositionFeatures, dynamic lines]
-
A.
compositionalFeature
Indicates that one entity is a structural or constituent feature that forms part of the composition or makeup of another entity.
-
B.
compositionDetail
chosen
Indicates that one entity specifies or describes the internal makeup, structure, or constituent elements of another entity.
-
C.
compositionStyle
Indicates the characteristic manner or approach in which something is composed, such as its structural, aesthetic, or stylistic conventions.
-
D.
featuredComposition
Indicates that one entity is highlighted or prominently presented as a notable composition in relation to another entity (such as a collection, event, or creator).
-
E.
compositionForm
Indicates the structural or organizational form in which something is composed or arranged.
- 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_69c6887fcddc8190a5d58908f6dee590 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e58a0a2c819088e0c8874fb4491f |
completed | March 27, 2026, 8:16 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c313e481908b61a23fc89f9332 |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:42 p.m.