Triple
T5769578
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Individual Taxpayer Identification Number |
E127293
|
entity |
| Predicate | numericRange |
P27293
|
FINISHED |
| Object | always begins with the digit 9 |
—
|
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: always begins with the digit 9 | Statement: [Individual Taxpayer Identification Number, numericRange, always begins with the digit 9]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numericRange Context triple: [Individual Taxpayer Identification Number, numericRange, always begins with the digit 9]
-
A.
rangeOf
Indicates that one entity specifies the set of possible values (range) that another entity’s outputs or properties can take.
-
B.
includesNumberingRange
Indicates that one entity contains or covers a specified contiguous range of numbers associated with another entity.
-
C.
hasRange
chosen
Indicates that a property or relation is constrained to take its values from a specified class, type, or value set.
-
D.
rangeType
Indicates the type or category of values that can appear in the range (output) position of a property or relation.
-
E.
rangeVariant
Indicates that one entity is a variant or alternative form within the value range defined or covered by another 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_69c00834f6308190851b0abeddd8ed7e |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02acb12c081908e4beee4a957f9f9 |
completed | March 22, 2026, 5:45 p.m. |
| PD | Predicate disambiguation | batch_69c021ce8d3c81909b332cb1c33a61ad |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:50 p.m.