Triple
T28623524
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Athens metropolitan area |
E724448
|
entity |
| Predicate | hasCentralAirport |
P42377
|
FINISHED |
| Object | Athens–Ben Epps Airport |
—
|
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: Athens–Ben Epps Airport | Statement: [Athens metropolitan area, hasCentralAirport, Athens–Ben Epps Airport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCentralAirport Context triple: [Athens metropolitan area, hasCentralAirport, Athens–Ben Epps Airport]
-
A.
hasMajorAirport
Indicates that a location possesses at least one significant airport that serves as a primary hub for air travel in that area.
-
B.
hasAirportCenter
Indicates that an airport is centrally located within, or serves as the main air transport hub for, a specified area or region.
-
C.
hasCoreAirport
chosen
Indicates that one entity designates another entity as its primary or central airport within a given context or network.
-
D.
hasRegionalAirport
Indicates that a place or region possesses or is served by a regional airport.
-
E.
isMajorRegionalAirportFor
Indicates that an airport serves as a primary or significant air travel hub for a particular region.
- 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_69f01d822ac08190932de59ec2268ed2 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f6c49627908190b3553474c7c3072b |
completed | May 3, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f23ae081909a52801266063a3c |
completed | May 3, 2026, 3:41 a.m. |
Created at: April 28, 2026, 4:34 a.m.