Triple
T5598935
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince Arthur, Duke of Brittany |
E147066
|
entity |
| Predicate | disputedHeirTo |
P7973
|
FINISHED |
| Object | English 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: English throne | Statement: [Prince Arthur, Duke of Brittany, disputedHeirTo, English throne]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: disputedHeirTo Context triple: [Prince Arthur, Duke of Brittany, disputedHeirTo, English throne]
-
A.
heirOf
Indicates that one entity is the legal or designated successor who inherits from another entity, typically upon that entity’s death or transfer of rights.
-
B.
associatedHeir
Indicates that one entity is designated or recognized as the heir connected to, or inheriting from, another entity.
-
C.
heldByHeirApparentOf
Indicates that something is possessed, controlled, or occupied by the heir apparent of a particular person, title, or position.
-
D.
dynasticClaim
chosen
Indicates a relationship where one party asserts a hereditary or lineage-based right to rule, inherit, or hold authority over another.
-
E.
adoptedAsHeir
Indicates that one entity has been formally chosen and accepted as the legal heir or successor 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_69c009043d648190a7af89698ccf1e3e |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c020d82870819087f9591b5a1021ce |
completed | March 22, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69c01b1890ec8190b9e6fa488792e4d4 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:38 p.m.