Triple
T35479889
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UP16 |
E1025440
|
entity |
| Predicate | rtoCode |
P183333
|
FINISHED |
| Object | 16 |
—
|
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: 16 | Statement: [UP16, rtoCode, 16]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rtoCode Context triple: [UP16, rtoCode, 16]
-
A.
stateCapitalRTOCodeExample
Indicates that a particular RTO (Regional Transport Office) code is used as an example associated with the state capital in a given context.
-
B.
raceCode
Indicates the classification of an entity according to a standardized race or ethnicity code.
-
C.
zoneCode
Indicates that an entity is associated with, or assigned to, a specific geographic or administrative zone identified by a code.
-
D.
railroadCodeFor
Indicates that a specific railroad code is assigned to or used to identify a particular railroad entity.
-
E.
regionCodeType
Indicates the classification or format type used for a given region code within a coding or identification system.
- 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_69f76dfadba0819083456aadcd6864ea |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79da9f80c8190b0afd8509f28747b |
completed | May 3, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69f79617d40481909ba372f94209c08b |
completed | May 3, 2026, 6:38 p.m. |
| PDg | Predicate description generation | batch_69f79da8d8848190ab5ab1bdad95d58c |
completed | May 3, 2026, 7:10 p.m. |
Created at: May 3, 2026, 4:04 p.m.