Triple
T37132643
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cebu–Caticlan |
E919564
|
entity |
| Predicate | isCommonlyMarketedAs |
P188501
|
FINISHED |
| Object | Cebu to Boracay flight route |
—
|
LITERAL FINISHED |
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: Cebu to Boracay flight route | Statement: [Cebu–Caticlan, isCommonlyMarketedAs, Cebu to Boracay flight route]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCommonlyMarketedAs Context triple: [Cebu–Caticlan, isCommonlyMarketedAs, Cebu to Boracay flight route]
-
A.
alsoMarketedIn
Indicates that a product or service is additionally marketed or sold in another specified market or region.
-
B.
isTypicallySoldAs
Indicates that one entity is commonly offered for sale in the form, packaging, or configuration represented by another entity.
-
C.
marketedFor
Indicates that something is promoted, advertised, or positioned as being intended or suitable for a particular use, audience, or purpose.
-
D.
marketedFrom
Indicates that a product, service, or offering began to be marketed starting from a specified time or date.
-
E.
marketedWith
Indicates that two or more products or services are promoted together as part of the same marketing effort or campaign.
- F. None of above. chosen
Provenance (4 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_69fba78aca4c8190b8f1831e8cc04e06 |
completed | May 6, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69fba34a65a4819088bac6c17542d71c |
completed | May 6, 2026, 8:23 p.m. |
| PDg | Predicate description generation | batch_69fba789c1188190973a919bfe2871f3 |
completed | May 6, 2026, 8:41 p.m. |
Created at: May 3, 2026, 4:15 p.m.