Triple
T33264062
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AERIS Holdings Costa Rica |
E851598
|
entity |
| Predicate | airportOperatedLocation |
P98428
|
FINISHED |
| Object | Alajuela |
—
|
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: Alajuela | Statement: [AERIS Holdings Costa Rica, airportOperatedLocation, Alajuela]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: airportOperatedLocation Context triple: [AERIS Holdings Costa Rica, airportOperatedLocation, Alajuela]
-
A.
airportUse
Indicates that an airport is used or utilized by a particular entity, such as an airline, organization, or service.
-
B.
servesAsPrimaryAirportOperatorForCity
Indicates that an entity functions as the main organization responsible for operating the primary airport serving a particular city.
-
C.
airportServed
Indicates that a particular airport provides service to, or is used for air travel to and from, a given location or area.
-
D.
airportLocationManaged
chosen
Indicates that the management or administrative control of an airport’s location is exercised by a particular authority or organization.
-
E.
operatingBaseAirport
Indicates the airport that serves as the primary base of operations for an airline or aircraft.
- 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_69f349642dac81908a37ffcc3b976a55 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7051ad6e4819095e82bbd64761803 |
completed | May 3, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69f700fe24e08190998e2c96fbaaad38 |
completed | May 3, 2026, 8:02 a.m. |
Created at: May 1, 2026, 1:32 a.m.