Triple
T26990938
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MIXAL |
E679857
|
entity |
| Predicate | supportsNumberRepresentation |
P5213
|
FINISHED |
| Object | integer |
—
|
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: integer | Statement: [MIXAL, supportsNumberRepresentation, integer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsNumberRepresentation Context triple: [MIXAL, supportsNumberRepresentation, integer]
-
A.
hasNumberSystem
chosen
Indicates that an entity possesses or uses a particular system for representing and organizing numbers.
-
B.
numericPartRepresents
Indicates that a numeric component of something stands for or encodes a specific value, property, or aspect of that thing.
-
C.
representsDigitsOf
Indicates that one entity encodes or corresponds to the individual digits that make up the numeric value of another entity.
-
D.
hasBaseRepresentation
Indicates that one value is expressed or encoded in terms of another value serving as its base or foundational representation.
-
E.
canRepresent
Indicates that one entity is capable of serving as a valid stand-in, proxy, or expression for another entity in a given context.
- 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_69eeeb5138ac8190b3c273ddc659a54f |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69fed357b2b4819084c709056a54461f |
completed | May 9, 2026, 6:25 a.m. |
| PD | Predicate disambiguation | batch_69fed103d9cc81909b11619745110c61 |
completed | May 9, 2026, 6:15 a.m. |
Created at: April 27, 2026, 6:51 a.m.