Triple
T13091995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Digital computer |
E310483
|
entity |
| Predicate | usesNumberSystem |
P5213
|
FINISHED |
| Object | Binary number system |
—
|
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: Binary number system | Statement: [Digital computer, usesNumberSystem, Binary number system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesNumberSystem Context triple: [Digital computer, usesNumberSystem, Binary number system]
-
A.
hasNumberSystem
chosen
Indicates that an entity possesses or uses a particular system for representing and organizing numbers.
-
B.
numberingSystemBasedOn
Indicates that one numbering system is derived from, structured according to, or conceptually dependent on another numbering system.
-
C.
usesNumeralsFrom
Indicates that one writing system, notation, or representation employs the numeral symbols originating from another system.
-
D.
laterNumberingSystem
Indicates that one numbering system was adopted or used after another, reflecting a subsequent or more recent scheme of numbering.
-
E.
usesPositionalNotation
Indicates that one entity represents numbers using a positional numeral system, where a digit’s value depends on its position.
- 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_69d806a733548190989cfd4ce981ca33 |
completed | April 9, 2026, 8:05 p.m. |
| NER | Named-entity recognition | batch_69d9813acbac8190b2fe5e07287457cf |
completed | April 10, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69d9803f6c508190bfadfbc2d00c2c64 |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 9:03 p.m.