Triple
T33569280
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marian exiles |
E859847
|
entity |
| Predicate | roleAfterReturn |
P116962
|
FINISHED |
| Object | leaders of Elizabethan Church |
—
|
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: leaders of Elizabethan Church | Statement: [Marian exiles, roleAfterReturn, leaders of Elizabethan Church]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleAfterReturn Context triple: [Marian exiles, roleAfterReturn, leaders of Elizabethan Church]
-
A.
roleAfterConversion
Indicates the role or position an entity holds after undergoing a conversion, transition, or change from a previous state or role.
-
B.
roleAfterManaging
Indicates the role or position an entity assumes after it has finished managing another entity or activity.
-
C.
roleAfterRAFClosure
Indicates that one entity holds a particular role or position in relation to another entity after the closure of the RAF (Royal Air Force) facility or organization in question.
-
D.
subsequentRole
Indicates that one role or position is held after, and in succession to, another role or position.
-
E.
returnedToRole
chosen
Indicates that an entity resumed or went back to a role or position it previously held.
- 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_69f3497c1d288190a844ea699914e038 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f74c70fd248190a9d5543afcb08211 |
completed | May 3, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69f7478e3b548190a51d5d436e2bb036 |
completed | May 3, 2026, 1:03 p.m. |
Created at: May 1, 2026, 1:40 a.m.