Triple
T20112443
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SH 209 |
E490366
|
entity |
| Predicate | isNumberInSystem |
P5213
|
FINISHED |
| Object | 209 in Colorado State Highways |
—
|
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: 209 in Colorado State Highways | Statement: [SH 209, isNumberInSystem, 209 in Colorado State Highways]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNumberInSystem Context triple: [SH 209, isNumberInSystem, 209 in Colorado State Highways]
-
A.
isInSystem
Indicates that one entity is located within, belongs to, or is contained by a particular system.
-
B.
hasNumberSystem
chosen
Indicates that an entity possesses or uses a particular system for representing and organizing numbers.
-
C.
containsNumber
Indicates that one entity includes or has at least one numeric value or digit within it.
-
D.
hasNumberInStructure
Indicates that an entity’s structure includes or contains a specific numerical value or component.
-
E.
isClassicNumber
Indicates that a number belongs to a traditionally recognized or canonical set of numbers defined as "classic" within a given context.
- 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_69da62636cc08190982cc71733a17b8d |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e666e21f908190b46c747662ff378a |
completed | April 20, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69e54cf788188190a46cc49c9ce7617f |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 11:29 p.m.