Triple
T31639087
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TAG |
E807394
|
entity |
| Predicate | previousAirportServed |
P81616
|
FINISHED |
| Object | Tagbilaran 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: Tagbilaran Airport | Statement: [TAG, previousAirportServed, Tagbilaran Airport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousAirportServed Context triple: [TAG, previousAirportServed, Tagbilaran Airport]
-
A.
previousAirportName
Indicates the name that an airport was known by before its current name.
-
B.
previousPrimaryAirportFor
chosen
Indicates that one airport was formerly the main or primary airport serving a particular location or entity before being replaced by another.
-
C.
hasFormerAirport
Indicates that an entity previously had an airport that is no longer in operation or no longer exists.
-
D.
previousPortOfCall
Indicates that a specified location was the last port where a vessel stopped or was registered before its current position or status.
-
E.
airportServed
Indicates that a particular airport provides service to, or is used for air travel to and from, a given location or area.
- 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_69f348d892948190915f8facacb9568c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fe744faca881908e11e90e0a35653f |
completed | May 8, 2026, 11:39 p.m. |
| PD | Predicate disambiguation | batch_69fe734cbf7081909a552c5cf3b5ea59 |
completed | May 8, 2026, 11:35 p.m. |
Created at: April 30, 2026, 10:48 p.m.