Triple
T37059967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Palazzo Reale |
E917295
|
entity |
| Predicate | hasConstructionPhases |
P44772
|
FINISHED |
| Object | medieval period |
—
|
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: medieval period | Statement: [Palazzo Reale, hasConstructionPhases, medieval period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasConstructionPhases Context triple: [Palazzo Reale, hasConstructionPhases, medieval period]
-
A.
hasMajorConstructionPhase
Indicates that an entity underwent a significant period of construction or major building activity during a specified time or phase.
-
B.
hasConstruction
Indicates that one entity possesses, contains, or is characterized by a particular construction, structure, or built form associated with it.
-
C.
constructionPhase
chosen
Indicates the specific stage or period an entity is in within an overall construction or building process.
-
D.
hasMultiplePhases
Indicates that the related process, event, or activity occurs in more than one distinct phase or stage.
-
E.
hasEndConstruction
Indicates that an entity is associated with, or terminates in, a specific construction or structural element at its end.
- 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_69f76e95fa40819091e14681087ae5e4 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a10036481909c71188b2a0e7f04 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:14 p.m.