Triple
T6094300
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TI-86 |
E135838
|
entity |
| Predicate | supportsNumberSystem |
P13398
|
FINISHED |
| Object | decimal |
—
|
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: decimal | Statement: [TI-86, supportsNumberSystem, decimal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsNumberSystem Context triple: [TI-86, supportsNumberSystem, decimal]
-
A.
hasNumberSystem
Indicates that an entity possesses or uses a particular system for representing and organizing numbers.
-
B.
hasNumberDistinction
Indicates that a language or system grammatically distinguishes between different numbers (such as singular, plural, dual, etc.) in its expressions.
-
C.
supportedSystem
chosen
Indicates that one entity provides compatibility, functionality, or operational support for another system.
-
D.
hasNumberOfWeekSystems
Indicates the relationship that specifies how many distinct week-based systems are associated with or used by a given entity.
-
E.
notationSystem
Indicates a relationship where one entity is the system or method of notation used to represent or encode another entity.
- 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_69c0087cd3c48190b459848c72d84eb1 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c05a9516ec819093e94ee8d3244e1b |
completed | March 22, 2026, 9:09 p.m. |
| PD | Predicate disambiguation | batch_69c049f3b1ec8190bea67a7bec6442a5 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:12 p.m.