Triple
T38389332
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hunsford |
E899665
|
entity |
| Predicate | governingPatron |
P64780
|
FINISHED |
| Object | Lady Catherine de Bourgh |
E260918
|
NE 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: Lady Catherine de Bourgh | Statement: [Hunsford, governingPatron, Lady Catherine de Bourgh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governingPatron Context triple: [Hunsford, governingPatron, Lady Catherine de Bourgh]
-
A.
patron of
Indicates a supportive relationship in which one entity provides sponsorship, protection, or backing to another, often enabling its activities or development.
-
B.
patronizedInstitution
Indicates that one entity regularly used, supported, or was a customer of a particular institution.
-
C.
patronRuler
Indicates a relationship where one entity serves as a protective or sponsoring ruler or sovereign authority over another.
-
D.
patroness
chosen
Indicates that a female person supports, sponsors, or acts as a benefactor for someone or something.
-
E.
governingHead
Indicates that one entity serves as the ruling or administrative authority over another entity, acting as its primary leader or head.
- F. None of above.
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_69f76e5c9b808190b486523f5c2f817d |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a41b2acf9f08190a8334729b9df8665 |
completed | June 28, 2026, 11:47 p.m. |
| PD | Predicate disambiguation | batch_6a037a1c850c819088795a7ae59bdeb8 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:31 p.m.