Triple
T8171548
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Palacio de Nava |
E190831
|
entity |
| Predicate | hasLaterAlterations |
P56192
|
FINISHED |
| Object | 17th century |
—
|
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: 17th century | Statement: [Palacio de Nava, hasLaterAlterations, 17th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLaterAlterations Context triple: [Palacio de Nava, hasLaterAlterations, 17th century]
-
A.
hasAlterationPeriod
chosen
Indicates that an entity is associated with a specific time span during which changes, modifications, or alterations may occur or are valid.
-
B.
laterModification
Indicates that one entity is a modification or revision that occurs after another in time.
-
C.
hasHumanModification
Indicates that an entity has been altered, influenced, or modified as a result of human activity or intervention.
-
D.
hasDesignChange
Indicates that an entity has undergone a modification or alteration to its original design.
-
E.
hasChangedOverTime
Indicates that the state, value, or characteristics of an entity or relationship have become different at some point across a period of time.
- 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_69ca82c1c0a08190bf8692b4d91a03ca |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb48056d0c819094575090a41e0083 |
completed | March 31, 2026, 4:05 a.m. |
| PD | Predicate disambiguation | batch_69cb36a4c40c81909f60aef0e1624c13 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:39 p.m.