Triple
T26194761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edward Stanley, 3rd Earl of Derby |
E655066
|
entity |
| Predicate | titleHeldAlso |
P177098
|
FINISHED |
| Object | Lord of Mann |
—
|
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: Lord of Mann | Statement: [Edward Stanley, 3rd Earl of Derby, titleHeldAlso, Lord of Mann]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleHeldAlso Context triple: [Edward Stanley, 3rd Earl of Derby, titleHeldAlso, Lord of Mann]
-
A.
titleHeldAs
Indicates that an entity holds or possesses a specific title in a particular capacity or role.
-
B.
titleHeldConcurrentlyWith
Indicates that one title or position was held at the same time as another title or position by the same entity.
-
C.
titleHeldTo
Indicates that one entity holds or possesses a specific title in relation to another entity or context.
-
D.
titleHeldAfter
Indicates that one entity held a particular title or position after another entity, establishing a temporal succession in holding that title.
-
E.
titleHeldThrough
Indicates that an entity holds or possesses a title by means of, or via the intermediary of, another entity or mechanism.
- 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_69ee5b48236c81908fe385b6afc4f60b |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f6f85bfba48190aba95b40642a8ca7 |
completed | May 3, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f6f65fd1d08190b88e5e68ba268500 |
completed | May 3, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69f6f854486c81909396d944a55e03ab |
completed | May 3, 2026, 7:25 a.m. |
Created at: April 26, 2026, 8:46 p.m.