Triple
T27954026
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Woodworking |
E703502
|
entity |
| Predicate | usesJointType |
P38738
|
FINISHED |
| Object | mortise and tenon 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: mortise and tenon joint | Statement: [Woodworking, usesJointType, mortise and tenon joint]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesJointType Context triple: [Woodworking, usesJointType, mortise and tenon joint]
-
A.
hasJointType
chosen
Indicates that one entity is associated with, or characterized by, a specific type or category of joint.
-
B.
isJointBodyOf
Indicates that an entity is a composite or shared governing or administrative body formed jointly by two or more other entities.
-
C.
isJointBase
Indicates that two or more components share a common base or foundation point.
-
D.
junctionType
Indicates the specific kind or configuration of a junction that relates connected elements or paths.
-
E.
isJointPosition
Indicates that an entity occupies or specifies a particular position or configuration within a joint (e.g., in a mechanical, robotic, or anatomical system).
- 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_69ef840c8b2c8190946ae9522774ba51 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f643ed0b7481908cf25f3afec0a61d |
completed | May 2, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69f641def1e88190a05bf865ced78b23 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 7:26 p.m.