Triple
T24328929
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Isabel Neville, Duchess of Clarence |
E613180
|
entity |
| Predicate | inheritanceClaim |
P68013
|
FINISHED |
| Object | Warwick estates |
—
|
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: Warwick estates | Statement: [Isabel Neville, Duchess of Clarence, inheritanceClaim, Warwick estates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inheritanceClaim Context triple: [Isabel Neville, Duchess of Clarence, inheritanceClaim, Warwick estates]
-
A.
legalSuccessorClaim
chosen
Indicates that one entity asserts it is the lawful successor or inheritor of another entity’s rights, status, or authority.
-
B.
lineageClaim
Indicates a claim or assertion that one entity is descended from, or belongs to the ancestral line of, another entity.
-
C.
mainClaim
Indicates that one statement is presented as the central or primary assertion being made about a topic.
-
D.
heritageClaimedBy
Indicates that a particular heritage, tradition, or cultural legacy is asserted or identified as belonging to a specific entity.
-
E.
recordClaim
Indicates that an entity formally documents or logs a claim made by another entity or about a particular matter.
- 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_69e2d7db6d5c819091194918157a7c1f |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f292ef86ec8190b27bc8cdff6c5c81 |
completed | April 29, 2026, 11:23 p.m. |
| PD | Predicate disambiguation | batch_69f287ad30048190b3ad3613486f277f |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 1:54 a.m.