Triple
T28485468
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cajidiocan |
E720816
|
entity |
| Predicate | hasIslandFeature |
P75555
|
FINISHED |
| Object | proximity to Mount Guiting-Guiting |
—
|
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: proximity to Mount Guiting-Guiting | Statement: [Cajidiocan, hasIslandFeature, proximity to Mount Guiting-Guiting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIslandFeature Context triple: [Cajidiocan, hasIslandFeature, proximity to Mount Guiting-Guiting]
-
A.
hasIsland
Indicates that one entity possesses, contains, or includes an island as part of its domain, territory, or structure.
-
B.
hasIslandCharacteristic
chosen
Indicates that an entity possesses a feature, quality, or attribute specifically associated with islands.
-
C.
isIsland
Indicates that the subject entity is classified as an island, i.e., a landmass surrounded by water.
-
D.
hasIslandConnection
Indicates that there exists a connection or link between entities that specifically involves or passes through an island.
-
E.
hasIslandArc
Indicates that one geographic or geological entity possesses or is associated with an island arc feature.
- 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_69f01a5a47148190b0a7e111bc432e0a |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f66d7765208190b87b1cc6d96a151c |
completed | May 2, 2026, 9:32 p.m. |
| PD | Predicate disambiguation | batch_69f66abfdaf08190a55f14c70be6fd4d |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 28, 2026, 2:58 a.m.