Triple
T33859019
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bulusan |
E867869
|
entity |
| Predicate | hasElevationVariation |
P50562
|
FINISHED |
| Object | from sea level to mountainous areas |
—
|
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: from sea level to mountainous areas | Statement: [Bulusan, hasElevationVariation, from sea level to mountainous areas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasElevationVariation Context triple: [Bulusan, hasElevationVariation, from sea level to mountainous areas]
-
A.
hasElevationFeature
chosen
Indicates that one entity possesses or is characterized by a particular elevation-related feature or attribute, such as height, altitude, or vertical relief.
-
B.
hasAltitudeDifference
Indicates that there is a specific vertical height difference between two entities or locations.
-
C.
elevationChange
Indicates a change in vertical position or altitude between two points or states.
-
D.
hasAverageElevation
Indicates that an entity is characterized by a specific mean height above a defined reference level, typically sea level.
-
E.
hasElevationData
Indicates that an entity is associated with specific elevation or height information, such as altitude values or elevation measurements.
- 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_69f349943ccc8190a3c41a3e0ae46cbf |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7bbf906d8819099020e548dd56bc9 |
completed | May 3, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a2dcf88190a7c9e109e41267be |
completed | May 3, 2026, 9:09 p.m. |
Created at: May 1, 2026, 1:47 a.m.