Triple
T36271424
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OM (Orchestra Model) guitar |
E892683
|
entity |
| Predicate | hasNeckJoin |
P61826
|
FINISHED |
| Object | 14‑fret neck joint |
—
|
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: 14‑fret neck joint | Statement: [OM (Orchestra Model) guitar, hasNeckJoin, 14‑fret neck joint]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNeckJoin Context triple: [OM (Orchestra Model) guitar, hasNeckJoin, 14‑fret neck joint]
-
A.
hasJunctionWith
Indicates that one entity meets or intersects with another at a shared junction point.
-
B.
hasNeckWood
Indicates that one entity uses or features a particular type of wood for its neck component.
-
C.
hasJunctionIn
Indicates that one entity contains or includes a junction located within the spatial or structural extent of another entity.
-
D.
neckJoint
chosen
Indicates a joint or connection located at or functioning as the neck between two body parts or structural elements.
-
E.
isJunction
Indicates that an entity functions as a junction point where multiple paths, lines, or connections meet or intersect.
- 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_69f76e488f34819083e254dbe288c27a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a005247dba08190acadf962bcefe4a0 |
completed | May 10, 2026, 9:39 a.m. |
| PD | Predicate disambiguation | batch_6a00519029848190a234358dfba45084 |
completed | May 10, 2026, 9:36 a.m. |
Created at: May 3, 2026, 4:09 p.m.