Triple
T4046876
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beaufort family |
E84086
|
entity |
| Predicate | hasClaimTo |
P40418
|
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: [Beaufort family, hasClaimTo, English throne]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasClaimTo Context triple: [Beaufort family, hasClaimTo, English throne]
-
A.
hasCentralClaim
Indicates that one entity presents or embodies the main assertion, thesis, or primary point made by another entity.
-
B.
supportsClaim
Indicates that one entity provides evidence, reasoning, or backing that strengthens or validates the truth or credibility of another entity’s claim.
-
C.
alsoClaimedBy
chosen
Indicates that the same item, statement, or resource is asserted or claimed by an additional party besides the primary one.
-
D.
claimsToBe
Indicates that one entity asserts or declares itself to have a particular identity, role, or property, regardless of whether this assertion is true.
-
E.
requiresClaim
Indicates that one entity can only be accessed, used, or fulfilled if a specific claim or entitlement has first been asserted or verified.
- 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_69aed930bd5c819083e7dcc14fc44f69 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefb62593c8190ab8462c4d9cd9d08 |
completed | March 9, 2026, 4:54 p.m. |
| PD | Predicate disambiguation | batch_69aef900386481909d04555a9ec9b0e3 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:37 p.m.