Triple
T36571801
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Richmond |
E902138
|
entity |
| Predicate | claimsThroneBy |
P68491
|
FINISHED |
| Object | hereditary right |
—
|
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: hereditary right | Statement: [Richmond, claimsThroneBy, hereditary right]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: claimsThroneBy Context triple: [Richmond, claimsThroneBy, hereditary right]
-
A.
claimedThroneAfter
Indicates that one entity assumed or asserted the right to a throne following the reign, death, or removal of another entity.
-
B.
reignClaim
chosen
Indicates a claim or assertion by an entity that it has the right to rule or hold sovereign authority over a domain or people.
-
C.
kingdomClaimed
Indicates that an entity has asserted ownership, control, or sovereign authority over a particular kingdom.
-
D.
securedThroneBy
Indicates that one entity obtained or maintained a throne or rulership position through the actions, support, or intervention of another entity.
-
E.
acceptedThrone
Indicates that an entity has agreed to assume and take on the role and authority associated with a throne or rulership.
- 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_69f76e6416708190a9754b8c52d4e453 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fcda3699948190adb57625bae08091 |
completed | May 7, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fd16d08190b0aca6e19a632e99 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:11 p.m.