Triple
T24069021
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cannikin |
E596172
|
entity |
| Predicate | devicePlacement |
P154739
|
FINISHED |
| Object | vertical shaft |
—
|
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: vertical shaft | Statement: [Cannikin, devicePlacement, vertical shaft]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: devicePlacement Context triple: [Cannikin, devicePlacement, vertical shaft]
-
A.
buttonPlacement
Indicates the spatial or positional arrangement of a button relative to other elements or within a given interface or context.
-
B.
platformLocation
Indicates the spatial position or placement of a platform relative to a reference point or environment.
-
C.
canonicalPlacement
Indicates the standard or preferred position or arrangement of one entity relative to another within a defined structure or system.
-
D.
plateLocation
Indicates the spatial position or placement of a plate relative to a reference location or object.
-
E.
batteryPlacement
Indicates the spatial or positional relationship specifying where a battery is located or installed relative to another object or system.
- F. None of above. chosen
Provenance (4 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_69e288c25c008190850cf447940ab181 |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1db15866c8190ab931216b8d9c57f |
completed | April 29, 2026, 10:19 a.m. |
| PD | Predicate disambiguation | batch_69f1764b1d4c8190b12590c6339c31c1 |
completed | April 29, 2026, 3:08 a.m. |
| PDg | Predicate description generation | batch_69f1785afe3c81909be28986ffe944bf |
completed | April 29, 2026, 3:17 a.m. |
Created at: April 17, 2026, 10:41 p.m.