Triple
T32732549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bayongbong |
E836991
|
entity |
| Predicate | mountainAccess |
P174745
|
FINISHED |
| Object | southern routes to Mount Cikuray |
—
|
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: southern routes to Mount Cikuray | Statement: [Bayongbong, mountainAccess, southern routes to Mount Cikuray]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mountainAccess Context triple: [Bayongbong, mountainAccess, southern routes to Mount Cikuray]
-
A.
endPointMountain
Indicates that a path, route, or boundary terminates at a mountain.
-
B.
controlledMountainPasses
Indicates that an entity had authority over and could regulate access through specific mountain passes.
-
C.
mountainType
Indicates the specific classification or category of a mountain based on its geological or physical characteristics.
-
D.
mountainFeature
Indicates that one entity is a notable physical or geographical feature associated with, located on, or forming part of a mountain.
-
E.
mountainListing
Indicates that a mountain is included in a specific catalog, list, or registry of mountains.
- F. None of above. chosen
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_69f34935fb048190ad4967420581f835 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6c9013da48190915619e554f079ff |
completed | May 3, 2026, 4:03 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f717a88190a924d614c2c9bca3 |
completed | May 3, 2026, 3:41 a.m. |
| PDg | Predicate description generation | batch_69f6c5fa10dc8190b2c06e4c701bd246 |
completed | May 3, 2026, 3:50 a.m. |
Created at: May 1, 2026, 1:11 a.m.