Triple
T17351316
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Savica Waterfall |
E421817
|
entity |
| Predicate | hasStairsOnAccessPath |
P22592
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Savica Waterfall, hasStairsOnAccessPath, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStairsOnAccessPath Context triple: [Savica Waterfall, hasStairsOnAccessPath, yes]
-
A.
hasStairway
chosen
Indicates that one entity includes or is connected to another entity by a stairway providing vertical access between levels.
-
B.
hasStairFunction
Indicates that one entity serves as a stair-related functional feature (e.g., providing access via stairs) for another entity.
-
C.
hasStaircaseType
Indicates the specific type or design classification of a staircase associated with an entity.
-
D.
hasStairsFacing
Indicates that one set of stairs is oriented toward or directly faces another object or direction.
-
E.
hasStepFreeAccess
Indicates that a location, facility, or route can be accessed without using stairs, typically via ramps, lifts, or level entrances.
- 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_69d889d520008190a26917a95bf1c2ea |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43a2ca0708190aae8306ec3a6f2a7 |
completed | April 19, 2026, 2:13 a.m. |
| PD | Predicate disambiguation | batch_69e3b02662d08190a07d0fb5c04b6f33 |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:44 a.m.