Triple
T14937288
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parr family |
E372427
|
entity |
| Predicate | politicalRoleOfMembers |
P72824
|
FINISHED |
| Object | courtier |
—
|
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: courtier | Statement: [Parr family, politicalRoleOfMembers, courtier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: politicalRoleOfMembers Context triple: [Parr family, politicalRoleOfMembers, courtier]
-
A.
roleInCongress
Indicates the specific position or function an individual holds within a legislative congress.
-
B.
politicalOrSocialRole
chosen
Indicates that an entity holds or is associated with a specific political or social position, function, or status within a group or society.
-
C.
electedMembers
Indicates that certain individuals have been chosen through an election process to serve as members of a specific body or organization.
-
D.
countryNationalRole
Indicates the official function, position, or responsibility that an entity holds at the national level within a specific country.
-
E.
hasPoliticalRole
Indicates that an entity holds, has held, or is assigned a specific political office, function, or position in relation to another entity or context.
- 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_69d85cc9da0c81908d583ca3f63a3908 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded64904d88190b6b4140da8e8199d |
completed | April 15, 2026, 12:05 a.m. |
| PD | Predicate disambiguation | batch_69de9a588c2c8190b1245a1c406f447c |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:37 a.m.