Triple
T20731653
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Villa Medici at Careggi |
E509585
|
entity |
| Predicate | languageOfHistoricalActivity |
P141287
|
FINISHED |
| Object | Italian |
—
|
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: Italian | Statement: [Villa Medici at Careggi, languageOfHistoricalActivity, Italian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOfHistoricalActivity Context triple: [Villa Medici at Careggi, languageOfHistoricalActivity, Italian]
-
A.
languageOfHistoricalRecord
Indicates the language in which a given historical record is written or recorded.
-
B.
historicalLanguage
Indicates that one language is a historical or earlier form/ancestor of another language.
-
C.
roleInLanguageHistory
Indicates the specific function, influence, or contribution an entity has had within the historical development or evolution of a language.
-
D.
languageOfHistoricName
Indicates the language in which a historic or former name of an entity is expressed.
-
E.
historicalLanguageOfHierarchy
Indicates that a language served as the traditional or historically established language used by a particular hierarchy or hierarchical institution.
- F. None of above. chosen
Provenance (4 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_69e0b4c589c08190834fb5d86d0efa2b |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c1ed7e8c8190974f2eb31a0a3106 |
completed | April 21, 2026, 12:16 a.m. |
| PD | Predicate disambiguation | batch_69e5c04b31248190b9b9d91b5cb854e3 |
completed | April 20, 2026, 5:57 a.m. |
| PDg | Predicate description generation | batch_69e5c3cbe5788190b7ace43bfdac2ef6 |
completed | April 20, 2026, 6:12 a.m. |
Created at: April 16, 2026, 12:30 p.m.