Triple
T15933983
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kalaw |
E386391
|
entity |
| Predicate | trekkingFeature |
P121048
|
FINISHED |
| Object | multi-day trekking routes |
—
|
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: multi-day trekking routes | Statement: [Kalaw, trekkingFeature, multi-day trekking routes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trekkingFeature Context triple: [Kalaw, trekkingFeature, multi-day trekking routes]
-
A.
mountainFeature
Indicates that one entity is a notable physical or geographical feature associated with, located on, or forming part of a mountain.
-
B.
hikingUse
Indicates the use or engagement in hiking as an activity or means of travel.
-
C.
isHikingDestination
Indicates that a location serves as a destination or endpoint for hiking activities or routes.
-
D.
rideFeature
Indicates that one entity is a feature, characteristic, or component associated with a particular ride.
-
E.
trekType
Indicates the specific category or style of trekking activity associated with an entity.
- 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_69d86da750008190987eb26be3f6c118 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e17d4d08f481909f38b75e3f42d9ab |
completed | April 17, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69e142d37cd88190ab50760f1783e20c |
completed | April 16, 2026, 8:13 p.m. |
| PDg | Predicate description generation | batch_69e17d48cc9c8190b03fd07ae2e9dfd8 |
completed | April 17, 2026, 12:22 a.m. |
Created at: April 10, 2026, 4:53 a.m.