Triple
T28116560
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Niesen |
E710648
|
entity |
| Predicate | stairwayPublicAccess |
P164564
|
FINISHED |
| Object | normally closed to the public |
—
|
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: normally closed to the public | Statement: [Niesen, stairwayPublicAccess, normally closed to the public]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stairwayPublicAccess Context triple: [Niesen, stairwayPublicAccess, normally closed to the public]
-
A.
hasStepFreeAccess
Indicates that a location, facility, or route can be accessed without using stairs, typically via ramps, lifts, or level entrances.
-
B.
hasStairway
Indicates that one entity includes or is connected to another entity by a stairway providing vertical access between levels.
-
C.
hasStairsFacing
Indicates that one set of stairs is oriented toward or directly faces another object or direction.
-
D.
hasPedestrianAccessTo
Indicates that a location or area can be reached or entered safely and directly by people on foot.
-
E.
hasStairFunction
Indicates that one entity serves as a stair-related functional feature (e.g., providing access via stairs) for another 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_69ef9b72f63081909dfbc2c1ddae86c6 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f64e6e8c9081908ce4d364aa26147a |
completed | May 2, 2026, 7:20 p.m. |
| PD | Predicate disambiguation | batch_69f64cacd2c08190aed8a1761d0da679 |
completed | May 2, 2026, 7:12 p.m. |
| PDg | Predicate description generation | batch_69f64db8ee1881909362701d72ffe282 |
completed | May 2, 2026, 7:17 p.m. |
Created at: April 27, 2026, 9:14 p.m.