Triple
T2724085
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Loretto Chapel |
E60148
|
entity |
| Predicate | hasHandrailAdded |
P13118
|
FINISHED |
| Object | later after original construction (staircase) |
—
|
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: later after original construction (staircase) | Statement: [Loretto Chapel, hasHandrailAdded, later after original construction (staircase)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHandrailAdded Context triple: [Loretto Chapel, hasHandrailAdded, later after original construction (staircase)]
-
A.
hasHandrails
chosen
Indicates that an object, structure, or pathway is equipped with handrails for support or safety.
-
B.
hasBalustrades
Indicates that one entity features or is equipped with balustrades as part of its structure or design.
-
C.
hasParapet
Indicates that an object, structure, or area is equipped with or bounded by a parapet (a low protective wall or barrier along an edge).
-
D.
hasStairway
Indicates that one entity includes or is connected to another entity by a stairway providing vertical access between levels.
-
E.
hasArm
Indicates that one entity possesses or is equipped with an arm as a physical part or component of itself.
- 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_69ab4b746d248190958e052045c09255 |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abdacc0a6881909b64a4d22e1d7690 |
completed | March 7, 2026, 7:59 a.m. |
| PD | Predicate disambiguation | batch_69abd82586f88190a98f60d3247fe2d3 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:55 p.m.