Triple
T18563879
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Counting Rod Numerals |
E453712
|
entity |
| Predicate | hasTensDigitOne |
P132509
|
FINISHED |
| Object | U+1D36A |
—
|
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+1D36A | Statement: [Counting Rod Numerals, hasTensDigitOne, U+1D36A]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTensDigitOne Context triple: [Counting Rod Numerals, hasTensDigitOne, U+1D36A]
-
A.
hasNumberOneSingleIn
Indicates that an entity has achieved at least one number-one single within a specified chart, region, or context.
-
B.
secondDigitRepresents
Indicates that the second digit in a numeric or coded value encodes or signifies a specific attribute, category, or meaning within that value.
-
C.
digitSymbolForOne
Indicates that something is the written or symbolic representation used to denote the numeric value one.
-
D.
isFirstNumberOneFor
Indicates that the first number in a given pair, sequence, or context is equal to one for the associated entity or situation.
-
E.
digitForNine
Indicates that something serves as or represents the numeral corresponding to the value nine.
- 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_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. |
| PDg | Predicate description generation | batch_69e484121cd48190bf583b4c94636a30 |
completed | April 19, 2026, 7:28 a.m. |
Created at: April 10, 2026, 11:42 a.m.