Triple
T34409661
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bedingfeld family |
E883218
|
entity |
| Predicate | endured |
P6390
|
FINISHED |
| Object | penal laws against Catholics |
—
|
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: penal laws against Catholics | Statement: [Bedingfeld family, endured, penal laws against Catholics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endured Context triple: [Bedingfeld family, endured, penal laws against Catholics]
-
A.
endures
Indicates that an entity continues to exist, persist, or remain in a particular state or condition over a period of time, often despite challenges or changes.
-
B.
endurance
Indicates the capacity of an entity to sustain an activity, state, or condition over an extended period without failure or significant loss of performance.
-
C.
underwent
chosen
Indicates that an entity experienced or was subjected to a process, event, or change, typically as the patient of an action.
-
D.
resistedUntil
Indicates that an entity continued to oppose or withstand another entity or force up to a specific point in time or event.
-
E.
undertook
Indicates that an entity assumed responsibility for starting and carrying out a task, project, or action.
- 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_69f349c1f2208190a09a489bb8b2719d |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71c35327c8190884f1bfe12bd2cd7 |
completed | May 3, 2026, 9:58 a.m. |
| PD | Predicate disambiguation | batch_69f71822d0e88190ac9731c7ae5a4def |
completed | May 3, 2026, 9:40 a.m. |
Created at: May 1, 2026, 1:59 a.m.