Triple
T26970372
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burrs |
E679298
|
entity |
| Predicate | mechanismOfAttachment |
P42077
|
FINISHED |
| Object | Mechanical interlocking |
—
|
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: Mechanical interlocking | Statement: [Burrs, mechanismOfAttachment, Mechanical interlocking]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mechanismOfAttachment Context triple: [Burrs, mechanismOfAttachment, Mechanical interlocking]
-
A.
attachedTo
Indicates that one entity is physically or logically fastened, connected, or joined to another entity.
-
B.
attachmentMethod
chosen
Indicates the way or technique by which one entity is fastened, joined, or secured to another.
-
C.
hingeType
Indicates the specific kind or configuration of hinge mechanism that connects two parts or surfaces.
-
D.
mechanismBy
Indicates that one entity occurs, is produced, or is brought about by means of another entity, which serves as its mechanism or causal process.
-
E.
typeOfFixing
Indicates the specific method or manner in which one entity is fastened, attached, or secured to another.
- 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_69eeeb4f3a448190b1e94b2d4776c16e |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f6212454348190905c6132f6191e76 |
completed | May 2, 2026, 4:07 p.m. |
| PD | Predicate disambiguation | batch_69f61b3ee7b08190a0a1bc5d26b757aa |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 6:38 a.m.