Triple
T14976749
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sir Thomas Parr |
E373466
|
entity |
| Predicate | household role |
P61538
|
FINISHED |
| Object | head of the Parr household at Kendal |
—
|
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: head of the Parr household at Kendal | Statement: [Sir Thomas Parr, household role, head of the Parr household at Kendal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: household role Context triple: [Sir Thomas Parr, household role, head of the Parr household at Kendal]
-
A.
houseRole
Indicates the functional role, purpose, or use that a house has within a given context or system.
-
B.
householdRoleOfMother
Indicates the specific role or function that a mother holds within the household context.
-
C.
household
Indicates that two or more entities belong to or are part of the same household unit, typically sharing a residence and domestic life.
-
D.
householdStaff
Indicates that one entity serves as domestic or household staff for another entity, typically within a private residence.
-
E.
familyOrganizerRole
chosen
Indicates the specific role or capacity an individual holds as the organizer or manager within a family group or household.
- 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_69d85ccbbcd48190acb56e7cf104d8ad |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded6fbd138819092254ea37388026c |
completed | April 15, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69de9a5d995881909e33658f5aea5582 |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:51 a.m.