Triple
T4558945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grand Staircase landing |
E120546
|
entity |
| Predicate | canBeAccessedBy |
P44172
|
FINISHED |
| Object | lower stair flight |
—
|
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: lower stair flight | Statement: [Grand Staircase landing, canBeAccessedBy, lower stair flight]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeAccessedBy Context triple: [Grand Staircase landing, canBeAccessedBy, lower stair flight]
-
A.
canAccedeTo
Indicates that one entity has the ability, permission, or right to gain access to or enter into another entity, resource, or state.
-
B.
hasAccessTo
Indicates that one entity is permitted to enter, use, or interact with another entity, resource, or location.
-
C.
hasAccessTowards
Indicates that one entity possesses the ability, permission, or means to reach, use, or interact with another entity or resource.
-
D.
areAccessibleAt
Indicates that certain entities can be reached, used, or entered at a specified location, time, or context.
-
E.
accessibleAs
chosen
Indicates that one entity can be reached, used, or obtained through another entity, often as an alternative form, route, or representation.
- 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_69bd4636f1648190a701445c2fcd9c17 |
completed | March 20, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69bd5829cc34819086ad2ae58446502e |
completed | March 20, 2026, 2:22 p.m. |
| PD | Predicate disambiguation | batch_69bd52254c648190a5144cfe8fa7e409 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:09 p.m.