Triple
T6951478
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Palais Lascaris |
E160933
|
entity |
| Predicate | hasOrnamentalStaircase |
P11048
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Palais Lascaris, hasOrnamentalStaircase, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOrnamentalStaircase Context triple: [Palais Lascaris, hasOrnamentalStaircase, yes]
-
A.
hasStairway
Indicates that one entity includes or is connected to another entity by a stairway providing vertical access between levels.
-
B.
hasStaircaseDesigner
Indicates that an entity has another entity that is responsible for designing its staircase.
-
C.
hasStairsFacing
Indicates that one set of stairs is oriented toward or directly faces another object or direction.
-
D.
hasStaircaseType
chosen
Indicates the specific type or design classification of a staircase associated with an entity.
-
E.
hasBalustrades
Indicates that one entity features or is equipped with balustrades as part of its structure or design.
- 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_69c68850419081909fb426b8f5a304c7 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6dacca12481908942ba793a104cc3 |
completed | March 27, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69c6d7bf0a7c8190b5ed4aca22ba9b97 |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:29 p.m.