Triple
T29405715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GNOME Calculator |
E745771
|
entity |
| Predicate | supportsNumberBase |
P5213
|
FINISHED |
| Object | binary |
—
|
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 | Statement: [GNOME Calculator, supportsNumberBase, binary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsNumberBase Context triple: [GNOME Calculator, supportsNumberBase, binary]
-
A.
hasNumberSystem
chosen
Indicates that an entity possesses or uses a particular system for representing and organizing numbers.
-
B.
logarithmBaseDetermines
Indicates that the chosen base of a logarithm determines how a quantity is expressed or scaled in logarithmic terms.
-
C.
numberingSystemBasedOn
Indicates that one numbering system is derived from, structured according to, or conceptually dependent on another numbering system.
-
D.
usesLogarithmBase
Indicates that one quantity or expression is defined, computed, or interpreted using a logarithm with a specified base.
-
E.
hasBaseRepresentation
Indicates that one value is expressed or encoded in terms of another value serving as its base or foundational representation.
- 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_69f0a79eb7d081908c67197a5f347e68 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_6a036c1282748190a820562bcd9aa5d9 |
completed | May 12, 2026, 6:06 p.m. |
| PD | Predicate disambiguation | batch_6a036bb5ca0c8190bd50abc197960b41 |
completed | May 12, 2026, 6:04 p.m. |
Created at: April 28, 2026, 2:54 p.m.