Triple
T34557514
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Snake Creek Gap |
E887245
|
entity |
| Predicate | railAccessObjective |
P101561
|
FINISHED |
| Object | Western and Atlantic Railroad near Resaca |
—
|
NE NERFINISHED |
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: Western and Atlantic Railroad near Resaca | Statement: [Snake Creek Gap, railAccessObjective, Western and Atlantic Railroad near Resaca]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railAccessObjective Context triple: [Snake Creek Gap, railAccessObjective, Western and Atlantic Railroad near Resaca]
-
A.
railAccessModel
Indicates the type or pattern of how rail infrastructure or services are accessed or connected between locations or entities.
-
B.
railwayAccess
Indicates that an entity has direct access to, connection with, or service by a railway line or station.
-
C.
hasRailOrRoadAccess
Indicates that an entity is connected to or reachable by either a railway network, a road network, or both.
-
D.
accessibleFromStation
Indicates that a location or facility can be reached directly or conveniently starting from a given station.
-
E.
railConnectionPurpose
chosen
Indicates the intended function or goal of a particular rail connection between locations or networks.
- 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_69f349d0c4d881908dd0950f5eb9ec0a |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7206085d08190bf62da716a91fdcb |
completed | May 3, 2026, 10:16 a.m. |
| PD | Predicate disambiguation | batch_69f71cc8074c81909ae09bea2acf1a09 |
completed | May 3, 2026, 10 a.m. |
Created at: May 1, 2026, 2:02 a.m.