Triple
T36271687
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Martin |
E892688
|
entity |
| Predicate | offersNeckJointType |
P61826
|
FINISHED |
| Object | dovetail 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: dovetail neck joint | Statement: [Martin, offersNeckJointType, dovetail neck joint]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offersNeckJointType Context triple: [Martin, offersNeckJointType, dovetail neck joint]
-
A.
neckJoint
chosen
Indicates a joint or connection located at or functioning as the neck between two body parts or structural elements.
-
B.
armType
Indicates the specific kind or configuration of an arm associated with an entity.
-
C.
neckDiameter
Indicates the width or thickness of an object's neck portion, typically measured as the diameter across that narrowed section.
-
D.
armAdjustability
Indicates that one entity’s arm component can be repositioned or configured in different ways relative to another entity or reference frame.
-
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_69f76e488f34819083e254dbe288c27a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fe744faca881908e11e90e0a35653f |
completed | May 8, 2026, 11:39 p.m. |
| PD | Predicate disambiguation | batch_69fe734cbf7081909a552c5cf3b5ea59 |
completed | May 8, 2026, 11:35 p.m. |
Created at: May 3, 2026, 4:09 p.m.