Triple
T25518025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Viscount Hinchingbrooke |
E639561
|
entity |
| Predicate | traditionalHolderFamilyName |
P60633
|
FINISHED |
| Object | Montagu |
—
|
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: Montagu | Statement: [Viscount Hinchingbrooke, traditionalHolderFamilyName, Montagu]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalHolderFamilyName Context triple: [Viscount Hinchingbrooke, traditionalHolderFamilyName, Montagu]
-
A.
familyNameIn
Indicates that an entity has a specified family name (surname) in a particular language or cultural context.
-
B.
secondHolderFamilyName
Indicates that the relationship specifies the family name (surname) of a second holder or secondary person associated with an entity.
-
C.
currentTitleHolderFamily
Indicates that one family is the present holder of a particular title, position, or honor.
-
D.
notableHolderFamily
Indicates that a particular family is notably associated with holding, possessing, or being custodians of the referenced entity.
-
E.
titleHeldByFamily
chosen
Indicates that a particular title, rank, or honor is held collectively or traditionally by a specific family or family line.
- 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_69e75dbe32e48190a62d749a0ff2a96a |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f69edbb7648190bd89c57e0932eac1 |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d17e8d48190b30bcc2f4bd81eb2 |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 21, 2026, 2:57 p.m.