Triple
T27751526
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gorkha Durbar |
E701223
|
entity |
| Predicate | hasStairwayAccessFrom |
P22592
|
FINISHED |
| Object | Gorkha Bazaar |
—
|
NE NERFINISHED |
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: Gorkha Bazaar | Statement: [Gorkha Durbar, hasStairwayAccessFrom, Gorkha Bazaar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStairwayAccessFrom Context triple: [Gorkha Durbar, hasStairwayAccessFrom, Gorkha Bazaar]
-
A.
hasStairway
chosen
Indicates that one entity includes or is connected to another entity by a stairway providing vertical access between levels.
-
B.
stairwayPublicAccess
Indicates that a stairway is accessible for use by the general public, without special permission or restriction.
-
C.
hasStairsFacing
Indicates that one set of stairs is oriented toward or directly faces another object or direction.
-
D.
hasEntranceOn
Indicates that one entity’s entrance or access point is located on or faces a specified side, boundary, or feature of another entity.
-
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.
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_69ef6a5193808190816eb7d0020b2d87 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69fcdf2394748190b35cead3e208447d |
completed | May 7, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe344ec8190a0471911952f4b82 |
completed | May 7, 2026, 6:37 p.m. |
Created at: April 27, 2026, 4:20 p.m.