Triple
T20780988
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nebraska–Wyoming border |
E511478
|
entity |
| Predicate | followsLatitude |
P34127
|
FINISHED |
| Object | 43rd parallel north |
—
|
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: 43rd parallel north | Statement: [Nebraska–Wyoming border, followsLatitude, 43rd parallel north]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsLatitude Context triple: [Nebraska–Wyoming border, followsLatitude, 43rd parallel north]
-
A.
parallelOfLatitude
chosen
Indicates that one entity is a line or circle on a sphere (typically Earth) that is at a constant latitude relative to another reference.
-
B.
followsRegion
Indicates that one region comes directly after another region in a defined order or sequence.
-
C.
followsCoast
Indicates that one entity’s path or boundary runs alongside and generally conforms to the shape of a coastline.
-
D.
follows
Indicates that one entity comes after, moves behind, or acts in accordance with another entity in time, space, or sequence.
-
E.
followsBy
Indicates that one event, state, or entity occurs or comes immediately after another in a sequence or order.
- 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_69e0b4cac7a48190a715cb3d545df2b4 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c287b5288190823766fe59402d48 |
completed | April 21, 2026, 12:19 a.m. |
| PD | Predicate disambiguation | batch_69e5c0550ec481908a0877fb2409d983 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:37 p.m.