Triple
T21186297
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Powis family |
E522087
|
entity |
| Predicate | socialRoleIn |
P143209
|
FINISHED |
| Object | landed gentry society of Wales |
—
|
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: landed gentry society of Wales | Statement: [Powis family, socialRoleIn, landed gentry society of Wales]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: socialRoleIn Context triple: [Powis family, socialRoleIn, landed gentry society of Wales]
-
A.
socialRoleInWork
Indicates the role or position an entity holds within a work-related or professional social context.
-
B.
socialRoleEmphasis
Indicates an emphasis on or prioritization of a particular social role within a relationship or interaction.
-
C.
identificationRole
Indicates that an entity serves as an identifier or plays a role in uniquely distinguishing or recognizing another entity.
-
D.
roleInName
Indicates that a specific role, title, or position is included as part of an entity’s name or naming expression.
-
E.
roleInText
Indicates that an entity participates in a text with a specific function or capacity (e.g., author, editor, character).
- F. None of above. chosen
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_69e0b50ef1d48190b063aa342667df22 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e73021671c8190a7b464ece7dbaadd |
completed | April 21, 2026, 8:06 a.m. |
| PD | Predicate disambiguation | batch_69e5f6027c248190a170a36612bd337e |
completed | April 20, 2026, 9:46 a.m. |
| PDg | Predicate description generation | batch_69e5f993240c8190847c0b08e65726c8 |
completed | April 20, 2026, 10:01 a.m. |
Created at: April 16, 2026, 3:06 p.m.