Triple
T28116561
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Niesen |
E710648
|
entity |
| Predicate | stairwayEvent |
P165124
|
FINISHED |
| Object | annual Niesenlauf stair run |
—
|
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: annual Niesenlauf stair run | Statement: [Niesen, stairwayEvent, annual Niesenlauf stair run]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stairwayEvent Context triple: [Niesen, stairwayEvent, annual Niesenlauf stair run]
-
A.
stairwayTheme
Indicates that something is associated with, characterized by, or thematically centered around a stairway or staircase.
-
B.
hasStairway
Indicates that one entity includes or is connected to another entity by a stairway providing vertical access between levels.
-
C.
hasStairFunction
Indicates that one entity serves as a stair-related functional feature (e.g., providing access via stairs) for another entity.
-
D.
stairwayPublicAccess
Indicates that a stairway is accessible for use by the general public, without special permission or restriction.
-
E.
numberOfStairs
Indicates the quantity of stairs associated with or present in a given context or structure.
- 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_69f65705a3048190a3728b695ba2ae65 |
completed | May 2, 2026, 7:56 p.m. |
| PD | Predicate disambiguation | batch_69f651a931748190a637e631a52bbfaa |
completed | May 2, 2026, 7:34 p.m. |
| PDg | Predicate description generation | batch_69f6562ef4e4819082ce6abd41b74dc5 |
completed | May 2, 2026, 7:53 p.m. |
Created at: April 27, 2026, 9:14 p.m.