Triple
T25528975
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nebraska Highway 66 |
E639857
|
entity |
| Predicate | westernOrientation |
P86279
|
FINISHED |
| Object | toward central Nebraska |
—
|
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: toward central Nebraska | Statement: [Nebraska Highway 66, westernOrientation, toward central Nebraska]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: westernOrientation Context triple: [Nebraska Highway 66, westernOrientation, toward central Nebraska]
-
A.
EasternView
Indicates a spatial relationship where one entity is oriented toward, faces, or has a view in the eastern direction relative to another reference point or area.
-
B.
westernCoastOn
Indicates that one entity is located on the western coast of another entity.
-
C.
regionalOrientation
chosen
Indicates how something is directed, aligned, or focused toward a particular geographic region or area.
-
D.
westernContinuation
Indicates that one entity is the western extension or continuation of another entity in space or geography.
-
E.
orientationOfDeity
Indicates the directional or positional alignment associated with a deity in relation to a reference point or 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_69e75dbf3f9c8190b3f2a75d1b75d127 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f861fa088190a77a182aa602703e |
completed | May 2, 2026, 1:13 p.m. |
| PD | Predicate disambiguation | batch_69f480789be08190ab252a6de3797200 |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 3:13 p.m.