Triple
T23388276
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holy Stairs |
E593942
|
entity |
| Predicate | hasSideStaircases |
P22592
|
FINISHED |
| Object | two parallel stairways for normal walking |
—
|
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: two parallel stairways for normal walking | Statement: [Holy Stairs, hasSideStaircases, two parallel stairways for normal walking]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSideStaircases Context triple: [Holy Stairs, hasSideStaircases, two parallel stairways for normal walking]
-
A.
hasStairway
chosen
Indicates that one entity includes or is connected to another entity by a stairway providing vertical access between levels.
-
B.
hasSpiralStaircase
Indicates that one entity contains or features a spiral staircase as part of its structure or design.
-
C.
hasStairsFacing
Indicates that one set of stairs is oriented toward or directly faces another object or direction.
-
D.
hasCanopiesAtStreetStairs
Indicates that canopies are present at the locations of street-level stairways.
-
E.
hasClimbSide
Indicates that one entity has a particular side or surface that is suitable or designated for climbing.
- 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_69e25d2754fc819085deea939bde60ab |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1a499bad88190afca1afb2e3fddb0 |
completed | April 29, 2026, 6:26 a.m. |
| PD | Predicate disambiguation | batch_69f061dde2e481908308952f9c0d3c2e |
completed | April 28, 2026, 7:29 a.m. |
Created at: April 17, 2026, 5:35 p.m.