Triple
T30111587
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baron Duras |
E765290
|
entity |
| Predicate | laterTitleHeldByHolder |
P197980
|
FINISHED |
| Object | Earl of Feversham |
—
|
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: Earl of Feversham | Statement: [Baron Duras, laterTitleHeldByHolder, Earl of Feversham]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterTitleHeldByHolder Context triple: [Baron Duras, laterTitleHeldByHolder, Earl of Feversham]
-
A.
lastHolderTitle
Indicates the official title or position held by the most recent holder of a given role, asset, or entity.
-
B.
laterTitleHolder
Indicates that one entity is a subsequent holder of a particular title or position previously held by another entity.
-
C.
titleHeldAs
Indicates that an entity holds or possesses a specific title in a particular capacity or role.
-
D.
titleHeldTo
Indicates that one entity holds or possesses a specific title in relation to another entity or context.
-
E.
titleHeldAfter
Indicates that one entity held a particular title or position after another entity, establishing a temporal succession in holding that title.
- F. None of above. chosen
Provenance (4 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_69f22475ad7c8190be7f9541044a0bbb |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fec00f27988190955de6b6348a4d97 |
completed | May 9, 2026, 5:03 a.m. |
| PD | Predicate disambiguation | batch_69febd52037c8190b475dbd50fdbc13e |
completed | May 9, 2026, 4:51 a.m. |
| PDg | Predicate description generation | batch_69fec00e5c1c819083d174bb4bc35f29 |
completed | May 9, 2026, 5:03 a.m. |
Created at: April 29, 2026, 7:10 p.m.