Triple
T35840966
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | George, Crown Prince of Serbia |
E1036075
|
entity |
| Predicate | causeOfLossOfHeirStatus |
P41735
|
FINISHED |
| Object | abdication |
—
|
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: abdication | Statement: [George, Crown Prince of Serbia, causeOfLossOfHeirStatus, abdication]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causeOfLossOfHeirStatus Context triple: [George, Crown Prince of Serbia, causeOfLossOfHeirStatus, abdication]
-
A.
reasonForLossOfSuccessionRights
chosen
Indicates the specific cause or circumstance that led to an individual losing their rights of succession.
-
B.
hadNoLegitimateHeirs
Indicates that the person died without any legally recognized offspring who could inherit their title, property, or rights.
-
C.
causeOfHusbandDeath
Indicates that the subject is the cause or reason for the husband’s death.
-
D.
lostImperialStatusOn
Indicates that an entity ceased to hold imperial status on a specific date or at a specific point in time.
-
E.
reasonForSuccession
Indicates the specific cause, circumstance, or justification that led one entity to succeed or replace another.
- 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_69f76e1a29e8819088280f26096aeb55 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd3d46d1f48190a1b20dd063224b7d |
completed | May 8, 2026, 1:32 a.m. |
| PD | Predicate disambiguation | batch_69fd3ae1510c81908fe1280efc17feee |
completed | May 8, 2026, 1:22 a.m. |
Created at: May 3, 2026, 4:06 p.m.