Triple
T24149714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mindoro Strait |
E598493
|
entity |
| Predicate | hasAdjacentProvince |
P95605
|
FINISHED |
| Object | Occidental Mindoro |
—
|
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: Occidental Mindoro | Statement: [Mindoro Strait, hasAdjacentProvince, Occidental Mindoro]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAdjacentProvince Context triple: [Mindoro Strait, hasAdjacentProvince, Occidental Mindoro]
-
A.
adjacentProvince
Indicates that two provinces share a common boundary and are directly next to each other geographically.
-
B.
hasNearbyProvince
chosen
Indicates that one province is geographically close to or directly adjacent to another province.
-
C.
hasNeighbouringState
Indicates that one state shares a common border or is directly adjacent geographically to another state.
-
D.
hasSisterProvince
Indicates that two provinces are related to each other as sister provinces, typically through a formal partnership or cooperative relationship.
-
E.
adjacentToProvinceCapital
Indicates that a location is directly next to or bordering the capital city of a 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_69e288c9e488819093dd1acd91b08b8a |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1e00e025c81908cacfcfa0819c73f |
completed | April 29, 2026, 10:40 a.m. |
| PD | Predicate disambiguation | batch_69f176585f3481909beb907de252cd98 |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 11:30 p.m.