Triple
T2453647
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Separatist congregation at Leiden |
E53765
|
entity |
| Predicate | reasonForRefuge |
P3057
|
FINISHED |
| Object | religious persecution in England |
—
|
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: religious persecution in England | Statement: [Separatist congregation at Leiden, reasonForRefuge, religious persecution in England]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForRefuge Context triple: [Separatist congregation at Leiden, reasonForRefuge, religious persecution in England]
-
A.
causeOfPersecution
Indicates that one entity is the reason or basis for another entity being persecuted.
-
B.
reasonForRelocation
chosen
Indicates the underlying cause, motivation, or circumstance that led an entity to move from one location to another.
-
C.
attemptedToSeekAsylumIn
Indicates that an entity tried, but may not have succeeded, to obtain asylum in a particular place or country.
-
D.
soughtAsylumAt
Indicates that an individual or group applied for protection or refuge at a particular country, institution, or authority.
-
E.
causeOfExile
Indicates the reason or circumstance that led to an entity’s exile.
- 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_69ab495d227c8190b26ae6548eeb1019 |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abd2bc7b5481908b3664495e99f1a4 |
completed | March 7, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69abd0aed2688190a18fe66b98d80e0b |
completed | March 7, 2026, 7:15 a.m. |
Created at: March 6, 2026, 9:44 p.m.