Triple
T34504727
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tirhuta digits |
E885849
|
entity |
| Predicate | numericProperty |
P179423
|
FINISHED |
| Object | European_Number (Unicode general category for digits) |
—
|
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: European_Number (Unicode general category for digits) | Statement: [Tirhuta digits, numericProperty, European_Number (Unicode general category for digits)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numericProperty Context triple: [Tirhuta digits, numericProperty, European_Number (Unicode general category for digits)]
-
A.
numericalProperty
Indicates that an entity is associated with a specific numeric value or measurable quantity.
-
B.
numericType
Indicates that one entity specifies or constrains the kind or category of numeric value associated with another entity.
-
C.
number
Indicates that one entity is associated with a specific numerical value or count in relation to another entity or context.
-
D.
hasNumericalValue
Indicates that an entity is associated with a specific numeric quantity or measurement.
-
E.
numberDescribedAs
Indicates that a number is characterized, labeled, or referred to using a particular description or phrase.
- 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_69f349cc0220819081f154c6964f4dc2 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f720cc1bfc8190a16118e3af8e9316 |
completed | May 3, 2026, 10:17 a.m. |
| PD | Predicate disambiguation | batch_69f71cc6397881909aaad37a9daa8a7e |
completed | May 3, 2026, 10 a.m. |
| PDg | Predicate description generation | batch_69f71fb0172c81908f23e95ff16b0dec |
completed | May 3, 2026, 10:13 a.m. |
Created at: May 1, 2026, 2:01 a.m.