Triple
T723066
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metropolitan Atlanta Rapid Transit Authority |
E14659
|
entity |
| Predicate | airportStation |
P18636
|
FINISHED |
| Object | Airport station |
—
|
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: Airport station | Statement: [Metropolitan Atlanta Rapid Transit Authority, airportStation, Airport station]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: airportStation Context triple: [Metropolitan Atlanta Rapid Transit Authority, airportStation, Airport station]
-
A.
hubAirport
Indicates that an airport serves as a primary hub or central operating base for a particular airline or carrier.
-
B.
airportOfficialName
Indicates the officially designated full name of an airport as recognized by authorities or governing bodies.
-
C.
airportIATAAssociated
Indicates that an airport is associated with a specific IATA (International Air Transport Association) code.
-
D.
airportLocatedIn
Indicates that an airport is geographically situated within a specific administrative or territorial area.
-
E.
airportServesAs
Indicates that an airport functions in a particular role or capacity (such as primary, secondary, or hub) for a specified area, organization, or service.
- F. None of above. chosen
Provenance (4 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_69a4934c753c81909b309027e48b9b3a |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a5a5360c8190b16e1e4f4206d0aa |
completed | March 1, 2026, 8:46 p.m. |
| PD | Predicate disambiguation | batch_69a4a4f700cc81908c6de3eedf68433c |
completed | March 1, 2026, 8:43 p.m. |
| PDg | Predicate description generation | batch_69a4a55a26e081908134ee93faaf7c40 |
completed | March 1, 2026, 8:45 p.m. |
Created at: March 1, 2026, 7:37 p.m.