Triple
T1690282
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Surface Duo |
E36535
|
entity |
| Predicate | hingeType |
P31362
|
FINISHED |
| Object | 360-degree hinge |
—
|
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: 360-degree hinge | Statement: [Surface Duo, hingeType, 360-degree hinge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hingeType Context triple: [Surface Duo, hingeType, 360-degree hinge]
-
A.
doorType
Indicates the specific kind or category of door associated with an entity.
-
B.
typeOfFixing
Indicates the specific method or manner in which one entity is fastened, attached, or secured to another.
-
C.
ridgeType
Indicates the specific morphological or structural category that a ridge belongs to within a classification of ridge forms.
-
D.
doorConfiguration
Indicates how a door is arranged or set up in relation to its frame, opening direction, and operational characteristics.
-
E.
hasHingedPlastronOrCarapace
Indicates that an entity possesses a plastron or carapace that is hinged, allowing parts of the shell to move relative to each other.
- 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_69a886151508819084fa7f1ce6e05577 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aaf3359ce48190803b322db8ad6027 |
completed | March 6, 2026, 3:31 p.m. |
| PD | Predicate disambiguation | batch_69aa61b71cec8190b273588051058ebd |
completed | March 6, 2026, 5:10 a.m. |
| PDg | Predicate description generation | batch_69aaf33347e48190a32b6d0099e3d389 |
completed | March 6, 2026, 3:30 p.m. |
Created at: March 4, 2026, 7:29 p.m.