Triple
T18563869
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Counting Rod Numerals |
E453712
|
entity |
| Predicate | hasDigitZero |
P29089
|
FINISHED |
| Object | U+1D360 |
—
|
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: U+1D360 | Statement: [Counting Rod Numerals, hasDigitZero, U+1D360]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDigitZero Context triple: [Counting Rod Numerals, hasDigitZero, U+1D360]
-
A.
hasIndependentDigitZero
Indicates that an entity possesses at least one digit or numeral component that is a zero considered as a distinct, standalone element.
-
B.
hasDigitSet
Indicates that an entity is associated with a specific set or collection of digits.
-
C.
isZeroFor
Indicates that a given value, expression, or function evaluates to zero when applied to or considered with respect to a specified entity or context.
-
D.
digitSymbolForZero
chosen
Indicates that something serves as the written digit symbol representing the numerical value zero.
-
E.
hasDigitCount
Indicates that one entity has a total number of digits equal to the value specified by the other 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_69d8d38974308190a9174430ef256b73 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e53afc57448190abd90167d7e12a18 |
completed | April 19, 2026, 8:28 p.m. |
| PD | Predicate disambiguation | batch_69e478c16e0c8190b03966aa23c395a6 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:42 a.m.