Triple
T28702149
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Decula Railroad station |
E729580
|
entity |
| Predicate | railStopFor |
P160597
|
FINISHED |
| Object | Dacula, Georgia |
—
|
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: Dacula, Georgia | Statement: [Decula Railroad station, railStopFor, Dacula, Georgia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railStopFor Context triple: [Decula Railroad station, railStopFor, Dacula, Georgia]
-
A.
railNetworkStopOn
chosen
Indicates that a rail stop or station is located on and served by a particular rail network.
-
B.
stopsAtStation
Indicates that a vehicle or service halts at a particular station as part of its route or schedule.
-
C.
railTerminus
Indicates that a railway line or service ends at a particular station or location, which serves as its final terminus.
-
D.
railTerminusFor
Indicates that one location serves as the final or terminal rail station or endpoint for a specified rail line or service.
-
E.
railLineTerminus
Indicates that a rail line ends or terminates at the specified location or station.
- 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_69f043e6e9688190b6bdd6e5665498ff |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f658ee40088190b71e1219407690d0 |
completed | May 2, 2026, 8:05 p.m. |
| PD | Predicate disambiguation | batch_69f65760fd3081908ffe014a5e2bf069 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 5:43 a.m.