Triple
T23308244
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Camiguin Airport |
E590508
|
entity |
| Predicate | servesIslandProvince |
P60499
|
FINISHED |
| Object | Camiguin |
—
|
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: Camiguin | Statement: [Camiguin Airport, servesIslandProvince, Camiguin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesIslandProvince Context triple: [Camiguin Airport, servesIslandProvince, Camiguin]
-
A.
islandServed
chosen
Indicates that a particular island is provided with service or coverage (such as transportation, utilities, or infrastructure) by a specified entity.
-
B.
servesProvince
Indicates that one entity (typically an organization, service, or administrative unit) provides service or has jurisdiction over a specified province.
-
C.
hasIslandProvince
Indicates that a region or country possesses an administrative province that is located on an island.
-
D.
isPartOfIslandProvince
Indicates that one entity is a constituent part or region within an island province.
-
E.
servedProvince
Indicates that an entity has provided services or held jurisdictional authority over a specified province.
- 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_69e25d1c0ecc8190a355aa229f06d0e0 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f197292fd08190bc364e1433dde213 |
completed | April 29, 2026, 5:29 a.m. |
| PD | Predicate disambiguation | batch_69effcf325f88190b320268c3c551abb |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 5:05 p.m.