Triple
T9366612
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Racconigi, Piedmont, Kingdom of Italy |
E225415
|
entity |
| Predicate | birthplaceOfTitle |
P1
|
FINISHED |
| Object | last King of Italy |
—
|
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: last King of Italy | Statement: [Racconigi, Piedmont, Kingdom of Italy, birthplaceOfTitle, last King of Italy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: birthplaceOfTitle Context triple: [Racconigi, Piedmont, Kingdom of Italy, birthplaceOfTitle, last King of Italy]
-
A.
placeOfBirth
chosen
Indicates the location where a person or other entity was born.
-
B.
nearBirthplaceOf
Indicates that one entity is located close to the place where another entity was born.
-
C.
creatorLivedIn
Indicates that the person who created a work resided in a particular place for some period of time.
-
D.
capitalOfOrigin
Indicates that one entity is the capital city associated with the origin (such as birthplace, founding place, or source location) of another entity.
-
E.
isBirthplaceRelatedTo
Indicates that there is a relationship between an entity and a birthplace, such as being born there or otherwise closely associated with that place of birth.
- 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_69ca842cbddc819099d71ecec48cf9e5 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd5042c89c8190994b12cf7600c366 |
completed | April 1, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_69cc7a6abb8c81908c7a2f4ee92cc949 |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:43 p.m.