Triple
T28854421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pozzo di San Patrizio |
E728695
|
entity |
| Predicate | staircaseType |
P11048
|
FINISHED |
| Object | double-helix 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: double-helix staircase | Statement: [Pozzo di San Patrizio, staircaseType, double-helix staircase]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: staircaseType Context triple: [Pozzo di San Patrizio, staircaseType, double-helix staircase]
-
A.
hasStaircaseType
chosen
Indicates the specific type or design classification of a staircase associated with an entity.
-
B.
materialUsedInStaircase
Indicates that a particular material is used in the construction or composition of a staircase.
-
C.
hasStairway
Indicates that one entity includes or is connected to another entity by a stairway providing vertical access between levels.
-
D.
stairwayTheme
Indicates that something is associated with, characterized by, or thematically centered around a stairway or staircase.
-
E.
hasStaircaseDesigner
Indicates that an entity has another entity that is responsible for designing its 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_69f0319f4e5481909e4c439dbe8be940 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f659db52f48190a610183087d3b39d |
completed | May 2, 2026, 8:08 p.m. |
| PD | Predicate disambiguation | batch_69f65762b5e481908a30ca963dcba4be |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 6:45 a.m.