Triple
T35131560
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sabangan, Mountain Province |
E1014448
|
entity |
| Predicate | isScenicRouteStop |
P118718
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Sabangan, Mountain Province, isScenicRouteStop, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isScenicRouteStop Context triple: [Sabangan, Mountain Province, isScenicRouteStop, true]
-
A.
isScenicStopOn
chosen
Indicates that a location serves as a designated scenic viewpoint or attraction situated along a particular route or path.
-
B.
hasScenicRouteStatus
Indicates that a route or path possesses a designated scenic status, typically recognized for its visual appeal or noteworthy landscapes.
-
C.
hasScenicRouteType
Indicates that a route is associated with a specific type or category of scenic quality or scenic designation.
-
D.
isScenicByway
Indicates that a roadway is officially designated as a scenic byway, recognized for its notable visual, cultural, or natural appeal along its route.
-
E.
hasScenicRoutes
Indicates that one location, path, or area offers routes that are visually attractive or notable for their natural or aesthetic scenery.
- 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_69f76dd9c1848190af70d4882a2c1ad7 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78c6a861881909f0f3de4e935bd0e |
completed | May 3, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69f78b9106008190930b3b3675b737d6 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 3, 2026, 4:02 p.m.