Triple
T5680616
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Voyage 200 TI-BASIC |
E125188
|
entity |
| Predicate | supportsProgrammingOnDevice |
P35060
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Voyage 200 TI-BASIC, supportsProgrammingOnDevice, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsProgrammingOnDevice Context triple: [Voyage 200 TI-BASIC, supportsProgrammingOnDevice, true]
-
A.
supportsDeviceManagement
Indicates that one entity provides capabilities or functionality to manage, configure, or control another entity’s devices.
-
B.
supportsProgramType
chosen
Indicates that one entity is capable of handling, offering, or being compatible with a specified type of program.
-
C.
usesDevice
Indicates that one entity operates, employs, or relies on a particular device to perform an action or achieve a purpose.
-
D.
usesSoftware
Indicates that one entity employs or operates a particular software application or system to perform tasks or functions.
-
E.
requiresDevice
Indicates that performing the specified action or relationship is contingent on the presence or use of a particular device.
- 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_69c0082a884c8190a79001bae658941f |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0248751bc8190b12aaa42d1ef17e3 |
completed | March 22, 2026, 5:19 p.m. |
| PD | Predicate disambiguation | batch_69c021be59088190a81c880957f666ab |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:44 p.m.