Triple
T6054396
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TI-85 |
E134872
|
entity |
| Predicate | supportsAssemblyProgramming |
P11868
|
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: [TI-85, supportsAssemblyProgramming, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsAssemblyProgramming Context triple: [TI-85, supportsAssemblyProgramming, true]
-
A.
hasAssembly
Indicates that an entity is composed of, or includes, one or more component parts assembled into a whole.
-
B.
programmedVia
Indicates that one entity is created, configured, or made to operate through the use of another entity as its programming method, tool, or medium.
-
C.
assemblyRequired
Indicates that the associated item or components must be put together or constructed before they can be used.
-
D.
supportedParadigm
chosen
Indicates that one entity (such as a tool, language, or system) provides functionality or features that enable or are compatible with a particular paradigm or methodological approach.
-
E.
supportsProgramType
Indicates that one entity is capable of handling, offering, or being compatible with a specified type of program.
- 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_69c00877b6d4819096b0e163728b73a3 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c05708fda48190ad3d1860969ebb6a |
completed | March 22, 2026, 8:54 p.m. |
| PD | Predicate disambiguation | batch_69c049edc6f0819092ca620d9073ad26 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:09 p.m.