Triple
T34500249
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mrs. Errol |
E885729
|
entity |
| Predicate | laterRelationshipWithEarlOfDorincourt |
P143393
|
FINISHED |
| Object | mutual respect |
—
|
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: mutual respect | Statement: [Mrs. Errol, laterRelationshipWithEarlOfDorincourt, mutual respect]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterRelationshipWithEarlOfDorincourt Context triple: [Mrs. Errol, laterRelationshipWithEarlOfDorincourt, mutual respect]
-
A.
relationshipToEarlJr
Indicates the specific familial or social relationship that an entity has to Earl Jr.
-
B.
titleHolderRelationshipToEarl
Indicates the familial or social relationship that the current title holder has to the Earl.
-
C.
laterPeerageConnections
chosen
Indicates that one entity acquires or forms peerage-related ties (such as titles, ranks, or noble associations) at a later time or stage in relation to another entity.
-
D.
successorAsEarlOfHuntingdon
Indicates that one person became the next Earl of Huntingdon following another person in that title or office.
-
E.
successorAsEarlOfMorton
Indicates the person who became the next Earl of Morton after the previous holder of the title.
- 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_69f349cc0220819081f154c6964f4dc2 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a002ae74da08190a4b47e0ff0f7f8fe |
completed | May 10, 2026, 6:51 a.m. |
| PD | Predicate disambiguation | batch_6a0029cc369c81909578e52c4a75ab18 |
completed | May 10, 2026, 6:46 a.m. |
Created at: May 1, 2026, 2:01 a.m.