Triple
T19377879
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crown in right of the Duchy of Lancaster |
E484717
|
entity |
| Predicate | mergedWithCrown |
P11440
|
FINISHED |
| Object | 1399 accession of Henry IV |
—
|
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: 1399 accession of Henry IV | Statement: [Crown in right of the Duchy of Lancaster, mergedWithCrown, 1399 accession of Henry IV]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mergedWithCrown Context triple: [Crown in right of the Duchy of Lancaster, mergedWithCrown, 1399 accession of Henry IV]
-
A.
crownUnionWith
chosen
Indicates the formal unification of two or more political entities under a single crown or sovereign authority.
-
B.
crownedWith
Indicates that one entity serves as a crown, top, or decorative upper covering placed upon another entity.
-
C.
crownedBy
Indicates that an entity is formally invested with a rank, title, or authority through a crowning ceremony performed by another entity.
-
D.
crownPresent
Indicates that a crown is currently present on or with the relevant entity.
-
E.
crownTransformedInto
Indicates that a crown undergoes a change of state or form, resulting in it becoming a different specified object or condition.
- 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_69d8e8d460d88190abf0591c5c9d2b0c |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e61a5dc3048190830b55c8ca02e624 |
completed | April 20, 2026, 12:21 p.m. |
| PD | Predicate disambiguation | batch_69e4fd54f8e48190956e73dd8969164a |
completed | April 19, 2026, 4:05 p.m. |
Created at: April 10, 2026, 1:35 p.m.