Triple
T37768445
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Geoffrey de Mandeville, 1st Earl of Essex |
E941478
|
entity |
| Predicate | wasGrantedTitleBy |
P3622
|
FINISHED |
| Object | King Stephen of England |
—
|
NE NERFINISHED |
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: King Stephen of England | Statement: [Geoffrey de Mandeville, 1st Earl of Essex, wasGrantedTitleBy, King Stephen of England]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasGrantedTitleBy Context triple: [Geoffrey de Mandeville, 1st Earl of Essex, wasGrantedTitleBy, King Stephen of England]
-
A.
authorizedByTitle
Indicates that an action or permission is granted based on a person’s role, position, or formal title rather than on individual identity.
-
B.
confersTitle
chosen
Indicates that one entity grants or bestows an official title or designation upon another entity.
-
C.
honoraryTitleGrantedTo
Indicates that an honorary title has been formally conferred upon a particular entity.
-
D.
dateGrantedHonorificTitle
Indicates the date on which an entity was formally awarded or granted an honorific title.
-
E.
nobleTitleGranted
Indicates that a noble title has been formally conferred upon an entity by an authorized grantor or authority.
- 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_69f76ee3251881909bb4451aad50752b |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbaf1b9fa48190b1f015c13060f925 |
completed | May 6, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69fbadf632ec8190b14991c971258307 |
completed | May 6, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:19 p.m.