Triple
T5147735
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fender Mike Dirnt Precision Bass |
E116114
|
entity |
| Predicate | headstock |
P56619
|
FINISHED |
| Object | Telecaster-style headstock |
—
|
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: Telecaster-style headstock | Statement: [Fender Mike Dirnt Precision Bass, headstock, Telecaster-style headstock]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: headstock Context triple: [Fender Mike Dirnt Precision Bass, headstock, Telecaster-style headstock]
-
A.
headstockShape
chosen
Indicates the specific contour or outline form of an object’s headstock relative to other parts or designs.
-
B.
headType
Indicates the specific kind or category of head associated with an entity (e.g., type of head part, head role, or head classification in a structure or system).
-
C.
heads
Indicates that one entity leads, directs, or is in charge of another entity, such as an organization, group, or initiative.
-
D.
headStatus
Indicates the current condition, role, or state of an entity in its capacity as a head or leader within a given context.
-
E.
headShape
Indicates the characteristic form or contour of an entity’s head.
- 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_69bd4446c0e08190a7c29dc74976bf03 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd78d7f4d081908d59adcd86f52f1d |
completed | March 20, 2026, 4:42 p.m. |
| PD | Predicate disambiguation | batch_69bd77ae2f10819098bb8939106e1281 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:43 p.m.