Triple
T26511394
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Upland station |
E669691
|
entity |
| Predicate | hasAtGradeCrossings |
P23561
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Upland station, hasAtGradeCrossings, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAtGradeCrossings Context triple: [Upland station, hasAtGradeCrossings, yes]
-
A.
hasGradeCrossings
chosen
Indicates that there are one or more level crossings where a road, path, or similar route intersects the railway or track at the same grade.
-
B.
hasAtGradeCrossingNearby
Indicates that one entity (typically a location or segment) has a nearby at-grade crossing where two transportation paths intersect at the same level.
-
C.
hasCrossingPoint
Indicates that two or more entities intersect or share at least one common point in space or along their paths.
-
D.
hadCrossingPoints
Indicates that two entities intersected or overlapped at one or more specific points in space or time.
-
E.
hasAlternativeCrossing
Indicates that there exists another available crossing option that can be used instead of the primary one.
- 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_69eeb319ec70819090834c2591cf5f1e |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f61392ec5081909382ace560650d77 |
completed | May 2, 2026, 3:09 p.m. |
| PD | Predicate disambiguation | batch_69f602d5c8808190a1fdbebd6f0981e8 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 27, 2026, 1:20 a.m.