Triple
T6230368
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Corduroy |
E139336
|
entity |
| Predicate | hasLoudSoftDynamics |
P51622
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Corduroy, hasLoudSoftDynamics, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLoudSoftDynamics Context triple: [Corduroy, hasLoudSoftDynamics, yes]
-
A.
hasDynamics
chosen
Indicates that one entity exhibits or is characterized by specific dynamic behavior, changes, or variations over time in relation to another entity or context.
-
B.
hasOrchestralFeature
Indicates that something includes, exhibits, or is characterized by a notable orchestral element or component.
-
C.
hasPartialSound
Indicates that one entity’s sound is included as a component or segment within the sound of another entity.
-
D.
hasAudioFeature
Indicates that one entity possesses or is associated with a specific audio-related characteristic or property.
-
E.
hasSound
Indicates that an entity produces, emits, or is associated with a particular sound.
- 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_69c008afd3148190b71e9eaa60420dd1 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c062d9a33c8190b66dbd89e0e3bbba |
completed | March 22, 2026, 9:44 p.m. |
| PD | Predicate disambiguation | batch_69c055ffdf54819086d987d646e44ff5 |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:22 p.m.