Triple
T23817181
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metropolitan Atlanta Rapid Transit Authority |
E589126
|
entity |
| Predicate | stationServesDowntown |
P68209
|
FINISHED |
| Object | Five Points station |
—
|
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: Five Points station | Statement: [Metropolitan Atlanta Rapid Transit Authority, stationServesDowntown, Five Points station]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stationServesDowntown Context triple: [Metropolitan Atlanta Rapid Transit Authority, stationServesDowntown, Five Points station]
-
A.
servesDowntownArea
chosen
Indicates that an entity provides service or coverage to the downtown area.
-
B.
isDowntownEndpointOf
Indicates that a location serves as the downtown terminus or endpoint of a route, line, or path.
-
C.
isDowntownHub
Indicates that a location functions as a central, primary hub within a city’s downtown area.
-
D.
hasDowntownLoopStation
Indicates that an entity includes or is served by a station located on a downtown loop transit line.
-
E.
isSuburbanStationOf
Indicates that a station is located in a suburban area and functionally serves as a subsidiary or outlying station of a main or central 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_69e25d18619081909c7fb89d8926f14a |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c7ab4e8881908f2711e9d62cad98 |
completed | April 29, 2026, 8:56 a.m. |
| PD | Predicate disambiguation | batch_69f156036ad48190bc2ffdaf39218bcb |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 7:58 p.m.