Triple
T5763129
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Palazzo Spada (courtyard modifications) |
E127143
|
entity |
| Predicate | actualHeight |
P9788
|
FINISHED |
| Object | significantly less than apparent height |
—
|
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: significantly less than apparent height | Statement: [Palazzo Spada (courtyard modifications), actualHeight, significantly less than apparent height]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: actualHeight Context triple: [Palazzo Spada (courtyard modifications), actualHeight, significantly less than apparent height]
-
A.
originalHeight
Indicates the initial or starting height of an entity before any change, adjustment, or transformation occurs.
-
B.
hasHeight
chosen
Indicates that one entity possesses a specific vertical measurement or stature.
-
C.
currentHeight
Indicates the present vertical measurement or elevation of an entity at a given point in time.
-
D.
totalHeight
Indicates the combined vertical measurement resulting from adding the heights of one or more entities.
-
E.
typicalHeight
Indicates the usual or characteristic height associated with an entity, such as a person, object, or species.
- 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_69c00833a3fc81908f4bc29ed011b7a6 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0293bbf2081908d40d76c4eb863ae |
completed | March 22, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69c021cc68648190bb86d049ebe80f12 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:49 p.m.