Triple
T27406344
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Interstate 84 |
E692009
|
entity |
| Predicate | stateAbbreviationSequence |
P180012
|
FINISHED |
| Object | OR–ID–UT |
—
|
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: OR–ID–UT | Statement: [Interstate 84, stateAbbreviationSequence, OR–ID–UT]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stateAbbreviationSequence Context triple: [Interstate 84, stateAbbreviationSequence, OR–ID–UT]
-
A.
areaAbbreviation
Indicates that one entity is an official abbreviated form or short code representing the named area of another entity.
-
B.
provinceState
Indicates that one entity is a province or state that is administratively contained within or associated with another, typically larger, territorial entity.
-
C.
hasPostalAbbreviationState
Indicates that a state is associated with a specific standardized postal abbreviation.
-
D.
stateNickname
Indicates that one entity is the commonly used nickname or informal moniker for a given state.
-
E.
postalStyleAbbreviation
Indicates that one term is a standardized shortened form of another term as used in postal addressing conventions.
- 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_69ef5205fc808190ad3efc5525b8e6d6 |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f7308a096081909d66a56f3c926806 |
completed | May 3, 2026, 11:24 a.m. |
| PD | Predicate disambiguation | batch_69f72a00c5f081908b6539d15baf4e12 |
completed | May 3, 2026, 10:57 a.m. |
| PDg | Predicate description generation | batch_69f730890a008190a882f7828f1c9162 |
completed | May 3, 2026, 11:24 a.m. |
Created at: April 27, 2026, 12:30 p.m.