Triple
T29984427
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Villa di Poggio Imperiale |
E761689
|
entity |
| Predicate | renovatedInPeriod |
P25681
|
FINISHED |
| Object | 18th 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: 18th century | Statement: [Villa di Poggio Imperiale, renovatedInPeriod, 18th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: renovatedInPeriod Context triple: [Villa di Poggio Imperiale, renovatedInPeriod, 18th century]
-
A.
renovatedAfter
Indicates that one entity was renovated at a later time than another entity.
-
B.
wasRenovatedFor
Indicates that an existing entity underwent renovation specifically to serve the needs, purposes, or use of another entity.
-
C.
renovationYear
Indicates the year in which an entity underwent renovation or significant refurbishment.
-
D.
renovationPeriod
chosen
Indicates the time span during which an object, structure, or entity undergoes renovation or refurbishment.
-
E.
renovatedBy
Indicates that an entity has been improved, restored, or updated through renovation work performed by another entity.
- 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_69f2246851148190b8e76206db94b105 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f678dc12c481909e88cb5cf37d5d29 |
completed | May 2, 2026, 10:21 p.m. |
| PD | Predicate disambiguation | batch_69f66ec9919881908a187bfc7c4df192 |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 29, 2026, 6:36 p.m.