Triple
T21674347
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tele |
E534928
|
entity |
| Predicate | hasNeckProfile |
P49300
|
FINISHED |
| Object | C-shaped neck |
—
|
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: C-shaped neck | Statement: [Tele, hasNeckProfile, C-shaped neck]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNeckProfile Context triple: [Tele, hasNeckProfile, C-shaped neck]
-
A.
neckCharacteristic
chosen
Indicates that an entity has a specific attribute, feature, or quality related to its neck.
-
B.
hasNeckWood
Indicates that one entity uses or features a particular type of wood for its neck component.
-
C.
hasCollarFunction
Indicates that one entity serves the role or function of a collar in relation to another entity.
-
D.
hasBackStraightOn
Indicates that one entity is positioned directly behind another, aligned straight along the same axis without any lateral offset.
-
E.
hasShoulderDiameter
Indicates the diameter measurement of an entity’s shoulder region or shoulder-related feature.
- 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_69e0c46898008190aa618a4af55bd1ee |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef8a0ed5388190b8f1932fb3f11c6a |
completed | April 27, 2026, 4:08 p.m. |
| PD | Predicate disambiguation | batch_69e6968abfdc81909cf9e0bd72db9eca |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:41 p.m.