Triple
T24646853
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Princess of Piedmont |
E610135
|
entity |
| Predicate | linkedToThroneOf |
P156902
|
FINISHED |
| Object | 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: Italy | Statement: [Princess of Piedmont, linkedToThroneOf, Italy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linkedToThroneOf Context triple: [Princess of Piedmont, linkedToThroneOf, Italy]
-
A.
linkedToThroneOf
chosen
Indicates a relationship where an entity is connected or related to a specific throne, typically through authority, succession, or symbolic association.
-
B.
throne
Indicates that an entity holds or occupies a position of sovereign authority or rulership, typically as a monarch.
-
C.
broughtToThroneBy
Indicates that an individual attained a throne or royal position through the actions, support, or intervention of another party.
-
D.
invitedToThrone
Indicates that one entity has been formally asked or summoned to be present at, or potentially take a role in, a throne or royal seat of power.
-
E.
securedThroneBy
Indicates that one entity obtained or maintained a throne or rulership position through the actions, support, or intervention of 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_69e2c4d350a481909170482bc2ce6af9 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f422aee0408190899efe7e24ef2b40 |
completed | May 1, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69f420e92cc88190a803aecdae78a051 |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 2:33 a.m.