Triple
T28116559
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Niesen |
E710648
|
entity |
| Predicate | stairwayClaim |
P160322
|
FINISHED |
| Object | one of the longest stairways in the world |
—
|
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: one of the longest stairways in the world | Statement: [Niesen, stairwayClaim, one of the longest stairways in the world]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stairwayClaim Context triple: [Niesen, stairwayClaim, one of the longest stairways in the world]
-
A.
towerClaim
Indicates that an entity asserts ownership, control, or rights over a specific tower.
-
B.
hasStairway
Indicates that one entity includes or is connected to another entity by a stairway providing vertical access between levels.
-
C.
attemptedClaim
Indicates that an entity made an effort to assert or demand a claim, regardless of whether the claim was ultimately accepted or successful.
-
D.
claimedFor
Indicates that one entity has asserted ownership, responsibility, or entitlement over or on behalf of another entity.
-
E.
stairwayTheme
chosen
Indicates that something is associated with, characterized by, or thematically centered around a stairway or staircase.
- 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_69ef9b72f63081909dfbc2c1ddae86c6 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f643ed0b7481908cf25f3afec0a61d |
completed | May 2, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69f641def1e88190a05bf865ced78b23 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 9:14 p.m.