Triple
T35025727
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lagangilang |
E1010330
|
entity |
| Predicate | hasMountainRangesNearby |
P651
|
FINISHED |
| Object | Cordillera Central |
—
|
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: Cordillera Central | Statement: [Lagangilang, hasMountainRangesNearby, Cordillera Central]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMountainRangesNearby Context triple: [Lagangilang, hasMountainRangesNearby, Cordillera Central]
-
A.
hasMountainPassNearby
Indicates that a mountain pass is located in close proximity to the referenced place or feature.
-
B.
hasHighestPointNear
Indicates that one entity’s highest point is located close to another specified entity or location.
-
C.
hasNotableNearbyMountain
Indicates that an entity is located near and is notably associated with a particular mountain.
-
D.
hasMountainRange
chosen
Indicates that one entity possesses, contains, or is geographically associated with a specific mountain range.
-
E.
hasNearestMountain
Indicates that one entity is the closest mountain geographically relative to another entity.
- 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_69f76dccf0108190af43b465d3750196 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fef2db323c8190821bda53f22a42be |
completed | May 9, 2026, 8:39 a.m. |
| PD | Predicate disambiguation | batch_69fef21d63c88190abf6a99b59b3c655 |
completed | May 9, 2026, 8:36 a.m. |
Created at: May 3, 2026, 4:01 p.m.