Triple
T31582394
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DECtape |
E805861
|
entity |
| Predicate | interfaceDevice |
P193132
|
FINISHED |
| Object | TU55 DECtape drive |
—
|
NE NERFINISHED |
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: TU55 DECtape drive | Statement: [DECtape, interfaceDevice, TU55 DECtape drive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: interfaceDevice Context triple: [DECtape, interfaceDevice, TU55 DECtape drive]
-
A.
interfaceElements
Indicates a relationship where certain elements function as components or parts of a user or system interface.
-
B.
structureDevice
Indicates a relationship in which a device is physically or functionally integrated into, supported by, or forming part of a larger structure.
-
C.
interfaceFamily
Indicates that one interface belongs to, or is categorized within, a particular family or group of related interfaces.
-
D.
interfaceToConsole
Indicates a relationship where an interface is connected or directed to a console for interaction or communication.
-
E.
typicalInterface
Indicates that one entity serves as the standard or commonly used interface through which another entity is accessed or interacted with.
- 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_69f348d3a86c8190a3e5e539a4dd125f |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fd389cb28c819099a77e28d25f258a |
completed | May 8, 2026, 1:13 a.m. |
| PD | Predicate disambiguation | batch_69fd3826d8048190ada79a5868d1d7f3 |
completed | May 8, 2026, 1:11 a.m. |
| PDg | Predicate description generation | batch_69fd389b653c81908a97ab2eff98c6ea |
completed | May 8, 2026, 1:12 a.m. |
Created at: April 30, 2026, 10:24 p.m.