Triple
T28475084
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Italian liberal state (1861–1922) |
E720539
|
entity |
| Predicate | thirdKing |
P15544
|
FINISHED |
| Object | Victor Emmanuel III of Italy |
—
|
NE NERFINISHED |
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: Victor Emmanuel III of Italy | Statement: [Italian liberal state (1861–1922), thirdKing, Victor Emmanuel III of Italy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: thirdKing Context triple: [Italian liberal state (1861–1922), thirdKing, Victor Emmanuel III of Italy]
-
A.
thirdMonarch
chosen
Indicates that the subject is the third monarch in a succession or lineage relative to a specified realm or dynasty.
-
B.
alsoKingOf
Indicates that an entity who is king of one place is simultaneously king of another place as well.
-
C.
仕えた君主
Indicates a relationship where someone served or was in the service of a particular lord or sovereign.
-
D.
kingOf
Indicates that one entity holds the position or role of king in relation to another entity, typically a territory, people, or domain.
-
E.
secondMonarch
Indicates that one entity is the second monarch (in chronological order of reign) in relation to another specified realm, dynasty, or succession context.
- 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_69f01a5983f48190b7c1b8857245a4f7 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f70e8755a48190931eaa77946f9460 |
completed | May 3, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f70abc00848190a1c3f495ef6c8dc6 |
completed | May 3, 2026, 8:43 a.m. |
Created at: April 28, 2026, 2:51 a.m.