Triple
T28110244
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bondoc Peninsula |
E710467
|
entity |
| Predicate | isCoastalLandformOf |
P60480
|
FINISHED |
| Object | Philippines |
—
|
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: Philippines | Statement: [Bondoc Peninsula, isCoastalLandformOf, Philippines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCoastalLandformOf Context triple: [Bondoc Peninsula, isCoastalLandformOf, Philippines]
-
A.
isCoastalLandmarkOf
Indicates that a landmark is located on or very near the coast of a specified geographic area or body of water.
-
B.
isPartOfCoastOf
chosen
Indicates that one entity forms a segment or component of the coastline belonging to another entity.
-
C.
isCoastalTo
Indicates that one place is located along or directly borders the coastline of another body of water or coastal region.
-
D.
connectsToCoastAt
Indicates that one entity has a direct physical or geographical connection or access to a coastline at the location of another entity.
-
E.
isCoastalLocation
Indicates that a location is situated on or directly adjacent to a sea, ocean, or significant coastal body of water.
- 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_69ef9b71fdb081908b4a61cd7ff147c1 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f640c75684819090935f5fb0716c29 |
completed | May 2, 2026, 6:21 p.m. |
| PD | Predicate disambiguation | batch_69f63c6a8474819091b8c6fe98e3862d |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 9:10 p.m.