Triple
T95918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edward VII |
E1929
|
entity |
| Predicate | heirApparentTo |
P2940
|
FINISHED |
| Object | British throne |
—
|
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: British throne | Statement: [Edward VII, heirApparentTo, British throne]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heirApparentTo Context triple: [Edward VII, heirApparentTo, British throne]
-
A.
heirApparentOf
chosen
Indicates that one entity is the officially recognized primary successor who is expected to inherit a title, position, or role from another entity.
-
B.
heirApparentDuringReign
Indicates that one entity was officially recognized as the designated heir apparent to another entity’s position or title during the latter’s period of reign.
-
C.
successorDynasty
Indicates that one dynasty directly follows and replaces another in a sequence of rule or authority.
-
D.
lastMonarchOf
Indicates that one entity is the final reigning monarch of another entity, such as a country, kingdom, or territory.
-
E.
successionOrder
Indicates the ordered sequence in which entities are designated to succeed or take over a role, position, or title.
- 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_69a24d4862f881908cc8b89d3a78031d |
completed | Feb. 28, 2026, 2:04 a.m. |
| NER | Named-entity recognition | batch_69a250cb400c8190b56343bbe19b48c7 |
completed | Feb. 28, 2026, 2:19 a.m. |
| PD | Predicate disambiguation | batch_69a24ebd19c48190bab291fea0ecc0c2 |
completed | Feb. 28, 2026, 2:11 a.m. |
Created at: Feb. 28, 2026, 2:09 a.m.