Triple
T1079923
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ASCII |
E23922
|
entity |
| Predicate | mostSignificantBit |
P23702
|
FINISHED |
| Object | 0 |
—
|
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: 0 | Statement: [ASCII, mostSignificantBit, 0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mostSignificantBit Context triple: [ASCII, mostSignificantBit, 0]
-
A.
majorVersion
Indicates that one entity specifies or corresponds to the primary (major) version number of another entity in a versioning scheme.
-
B.
isMajor
Indicates that an entity holds primary or greater significance, importance, or rank relative to others in a given context.
-
C.
isLargestOf
Indicates that one entity has the greatest size, extent, or magnitude among a specified set of entities.
-
D.
bitWidth
Indicates the number of bits used to represent or encode a given value, type, or data element.
-
E.
isMaximumWhen
Indicates that a quantity or function reaches its greatest possible value under specified conditions or at a particular point.
- F. None of above. chosen
Provenance (4 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_69a493f1ddf48190a99d54b00e99f8ce |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b94509d08190964509ea4a2d7912 |
completed | March 1, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69a4b73d9f08819093668104f129840e |
completed | March 1, 2026, 10:01 p.m. |
| PDg | Predicate description generation | batch_69a4b80f0fb08190a19a50e38ae8f16c |
completed | March 1, 2026, 10:05 p.m. |
Created at: March 1, 2026, 7:42 p.m.