Triple
T29658153
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gunung Mat Cincang |
E750326
|
entity |
| Predicate | hasStructureOnSlope |
P83773
|
FINISHED |
| Object | Langkawi Sky Bridge |
—
|
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: Langkawi Sky Bridge | Statement: [Gunung Mat Cincang, hasStructureOnSlope, Langkawi Sky Bridge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStructureOnSlope Context triple: [Gunung Mat Cincang, hasStructureOnSlope, Langkawi Sky Bridge]
-
A.
isOnSlopeOf
chosen
Indicates that one entity is located on the inclined surface or side of another entity, typically a sloping terrain or structure.
-
B.
hasSettlementOnSlopes
Indicates that a settlement is located on or extends across the slopes of a landform such as a hill or mountain.
-
C.
hasSlopeFeature
Indicates that an entity possesses or is characterized by a particular slope-related property or feature.
-
D.
hasSlopeProtection
Indicates that a slope or embankment is equipped with protective measures or structures to prevent erosion, instability, or damage.
-
E.
hasIncline
Indicates that one entity possesses or exhibits a slope, tilt, or upward/downward angle relative to another reference.
- 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_69f0d6226fe881908819197c9ef9ee04 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fdd5fba5048190b7d430ae2054a1fd |
completed | May 8, 2026, 12:24 p.m. |
| PD | Predicate disambiguation | batch_69fdd35f76f88190a1854ea27132f9c7 |
completed | May 8, 2026, 12:13 p.m. |
Created at: April 28, 2026, 6:56 p.m.