Triple
T37132639
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cebu–Caticlan |
E919564
|
entity |
| Predicate | hasArrivalLocation |
P1522
|
FINISHED |
| Object | Caticlan Airport terminal |
—
|
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: Caticlan Airport terminal | Statement: [Cebu–Caticlan, hasArrivalLocation, Caticlan Airport terminal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasArrivalLocation Context triple: [Cebu–Caticlan, hasArrivalLocation, Caticlan Airport terminal]
-
A.
hasArrivalArea
Indicates that an entity is associated with a specific area designated for arrivals, such as where incoming people or items first enter or are received.
-
B.
hasArrivalAirport
Indicates the airport at which a journey, flight, or trip concludes or arrives.
-
C.
arrivalLocationType
Indicates the type or category of place where an arrival occurs in the described relationship or event.
-
D.
placeOfArrival
chosen
Indicates the location at which an entity or person arrives at the end of a journey, movement, or transfer.
-
E.
isMainArrivalPointFor
Indicates that a location serves as the primary arrival point for a given entity or flow of entities.
- 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_69f76e9d13e48190a108f7fbf80ff375 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fe91383a1c81909266e40c3c3ede6c |
completed | May 9, 2026, 1:43 a.m. |
| PD | Predicate disambiguation | batch_69fe8fde094081908f0f121664fbb5c7 |
completed | May 9, 2026, 1:37 a.m. |
Created at: May 3, 2026, 4:15 p.m.