Triple
T23817166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metropolitan Atlanta Rapid Transit Authority |
E589126
|
entity |
| Predicate | beganRailService |
P30642
|
FINISHED |
| Object | 1979 |
—
|
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: 1979 | Statement: [Metropolitan Atlanta Rapid Transit Authority, beganRailService, 1979]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: beganRailService Context triple: [Metropolitan Atlanta Rapid Transit Authority, beganRailService, 1979]
-
A.
openedAsRailroad
Indicates that a transportation line or route was originally inaugurated and operated as a railroad.
-
B.
blueLineServiceBegan
Indicates that service on the Blue Line began operating at a specified time or event.
-
C.
inauguratedHighSpeedServiceIn
Indicates that an entity began or officially launched high-speed service (such as transportation or communication) in a specified location or region.
-
D.
railwayLineOpened
chosen
Indicates that a railway line began official operation or service on a specified date.
-
E.
servedByRailroad
Indicates that a location or facility is provided with transportation or service by a railroad line or company.
- 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.