Triple
T29325999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | English horn |
E743643
|
entity |
| Predicate | isCharacteristicFor |
P56672
|
FINISHED |
| Object | expressive lyrical solos |
—
|
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: expressive lyrical solos | Statement: [English horn, isCharacteristicFor, expressive lyrical solos]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCharacteristicFor Context triple: [English horn, isCharacteristicFor, expressive lyrical solos]
-
A.
hasCharacteristic
Indicates that an entity possesses, exhibits, or is defined by a particular attribute, feature, or quality.
-
B.
describesCharacteristicOf
chosen
Indicates that one entity expresses or specifies a characteristic, feature, or property of another entity.
-
C.
subjectHasCharacteristic
Indicates that a subject possesses, exhibits, or is defined by a particular characteristic or attribute.
-
D.
characteristicDevice
Indicates that a device is a defining or typical instrument, tool, or equipment associated with a particular entity, context, or activity.
-
E.
entityCharacteristic
Indicates that an entity possesses, exhibits, or is defined by a particular characteristic or attribute.
- 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_69f09125f784819080f4e9fce9fe624f |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f66895a0d481908efba5930e1ec3b9 |
completed | May 2, 2026, 9:11 p.m. |
| PD | Predicate disambiguation | batch_69f660f2e3708190ab658652bcfc04d0 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 1:26 p.m.