Triple
T16302321
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dudley family |
E395821
|
entity |
| Predicate | fateOfKeyMember |
P22875
|
FINISHED |
| Object | Edmund Dudley executed in 1510 |
—
|
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: Edmund Dudley executed in 1510 | Statement: [Dudley family, fateOfKeyMember, Edmund Dudley executed in 1510]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fateOfKeyMember Context triple: [Dudley family, fateOfKeyMember, Edmund Dudley executed in 1510]
-
A.
fateOfMembers
Indicates the outcome, destiny, or final status experienced by the members of a group or collection.
-
B.
keyMember
Indicates that an entity plays a central, highly important, or leading role within a group, organization, or structure.
-
C.
keyPerson
Indicates that a person plays a primary, central, or critically important role in relation to an organization, project, or entity.
-
D.
fateOfLeaders
chosen
Indicates the ultimate outcome or destiny that befalls leaders, such as their end, removal, or final status.
-
E.
hasMemberWhoBecame
Indicates that a group or organization includes at least one member who later attained or transitioned into a specified role, status, or affiliation.
- 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_69d87f23bb088190a16fbb91a1957ea5 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e25e3404288190a7106d62c15c3193 |
completed | April 17, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69e219fa5508819097e9d383348bf174 |
completed | April 17, 2026, 11:31 a.m. |
Created at: April 10, 2026, 5:06 a.m.