Triple
T34271794
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oregon Route 208 |
E879335
|
entity |
| Predicate | isPartOfNumberedSystem |
P22578
|
FINISHED |
| Object | Oregon numbered highway system |
—
|
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: Oregon numbered highway system | Statement: [Oregon Route 208, isPartOfNumberedSystem, Oregon numbered highway system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPartOfNumberedSystem Context triple: [Oregon Route 208, isPartOfNumberedSystem, Oregon numbered highway system]
-
A.
isNumberedBy
Indicates that an entity is assigned, identified, or organized by a specific number or numbering scheme.
-
B.
hasNumberSystem
Indicates that an entity possesses or uses a particular system for representing and organizing numbers.
-
C.
numberingSystemBasedOn
Indicates that one numbering system is derived from, structured according to, or conceptually dependent on another numbering system.
-
D.
isNumbered
chosen
Indicates that an entity has been assigned a specific number or position in an ordered sequence.
-
E.
hasCatalogNumberSystem
Indicates that an entity uses or is associated with a particular catalog numbering system for organizing or identifying items.
- 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_69f349b4f5fc819094b441d18e95e5f1 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff4fc6077c8190b8fd9b43fcfde986 |
completed | May 9, 2026, 3:16 p.m. |
| PD | Predicate disambiguation | batch_69ff4e61fb648190a72f7918961ece9c |
completed | May 9, 2026, 3:10 p.m. |
Created at: May 1, 2026, 1:56 a.m.