Triple
T4454065
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fender Stratocaster |
E97679
|
entity |
| Predicate | bodyContour |
P56613
|
FINISHED |
| Object | comfort-contoured body |
—
|
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: comfort-contoured body | Statement: [Fender Stratocaster, bodyContour, comfort-contoured body]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bodyContour Context triple: [Fender Stratocaster, bodyContour, comfort-contoured body]
-
A.
hasBodyRegion
Indicates that an entity possesses, includes, or is associated with a specific anatomical or bodily region.
-
B.
bodyVariant
Indicates that one entity is an alternative physical form or version of another entity’s body.
-
C.
seatOfBody
Indicates that one entity serves as the physical location or base where another entity (typically an organization or authority) is situated or headquartered.
-
D.
bodyCovering
Indicates the type of external covering or surface (such as skin, fur, feathers, or scales) that characterizes an entity’s body.
-
E.
parentBodyType
Indicates that one entity has a body type that serves as the parent or base classification from which another entity's body type is derived or organized.
- F. None of above. chosen
Provenance (4 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_69b3454777808190b78aa9047ba1f018 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b355f669948190b14ef42e8dbca525 |
completed | March 13, 2026, 12:10 a.m. |
| PD | Predicate disambiguation | batch_69b34f649df081909d3cc2f6a1b8f282 |
completed | March 12, 2026, 11:42 p.m. |
| PDg | Predicate description generation | batch_69b354e1f0948190b645096b2b7037af |
completed | March 13, 2026, 12:05 a.m. |
Created at: March 12, 2026, 11:33 p.m.