Triple
T37597370
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metro Iloilo–Guimaras |
E935427
|
entity |
| Predicate | hasMainlandProvince |
P98125
|
FINISHED |
| Object | Iloilo |
E274903
|
NE 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: Iloilo | Statement: [Metro Iloilo–Guimaras, hasMainlandProvince, Iloilo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainlandProvince Context triple: [Metro Iloilo–Guimaras, hasMainlandProvince, Iloilo]
-
A.
hasAdjacentMainlandArea
Indicates that one geographic area directly borders or touches a contiguous mainland region.
-
B.
isMainlandTerritoryOf
Indicates that a territory constitutes the primary continental landmass belonging to a particular country or sovereign entity.
-
C.
hasIslandProvince
Indicates that a region or country possesses an administrative province that is located on an island.
-
D.
hasProvinceOrRegion
chosen
Indicates that one entity includes, is associated with, or is located within a specific province or region as an administrative or geographic subdivision.
-
E.
hasAccessToMainland
Indicates that an entity is able or permitted to reach, enter, or use the mainland from another location.
- F. None of above.
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_69f76ecf39c081909baffe597bb55273 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a423f6d4be48190ae194b01395bd52f |
completed | June 29, 2026, 9:48 a.m. |
| PD | Predicate disambiguation | batch_6a037a1553e08190bb7424c448cb1f33 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:18 p.m.