Triple
T22902955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | William Neville, Earl of Kent |
E568371
|
entity |
| Predicate | reasonForTitleGrant |
P15925
|
FINISHED |
| Object | military service to the Yorkist cause |
—
|
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: military service to the Yorkist cause | Statement: [William Neville, Earl of Kent, reasonForTitleGrant, military service to the Yorkist cause]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForTitleGrant Context triple: [William Neville, Earl of Kent, reasonForTitleGrant, military service to the Yorkist cause]
-
A.
reasonForTitle
chosen
Indicates the justification, cause, or basis for assigning a particular title to an entity.
-
B.
reasonForGrant
Indicates the justification, purpose, or cause for which a grant is awarded or provided.
-
C.
reasonForHonorific
Indicates the reason, justification, or basis for which an honorific title or form of address is granted to or used for an entity.
-
D.
specialAwardReason
Indicates the specific reason or justification for which a special award is given to an entity.
-
E.
reasonForName
Indicates the explanation or cause behind why an entity has a particular name.
- 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_69e2458cd9e48190943ad2e34485d939 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f18017a0208190a7e6f1638fc17b01 |
completed | April 29, 2026, 3:50 a.m. |
| PD | Predicate disambiguation | batch_69ef3b6b2e2481908258156937b5a745 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:41 p.m.