Triple
T18142669
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Penal Laws in Ireland |
E434300
|
entity |
| Predicate | encouragedConversionTo |
P45854
|
FINISHED |
| Object | Protestantism |
—
|
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: Protestantism | Statement: [Penal Laws in Ireland, encouragedConversionTo, Protestantism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: encouragedConversionTo Context triple: [Penal Laws in Ireland, encouragedConversionTo, Protestantism]
-
A.
helpedConvert
Indicates that one entity assisted another in changing, transforming, or transitioning something from one state, form, or system to another.
-
B.
involvesConversionTo
Indicates that one entity undergoes a change of form, type, or state resulting in another entity.
-
C.
reasonForConversion
chosen
Indicates the cause, motivation, or justification behind a particular conversion event or change.
-
D.
convertedIn
Indicates that one entity has been transformed, changed, or translated into another form, state, or representation within a specified context.
-
E.
allowsConversionTo
Indicates that one entity permits or enables transformation or change into another specified form or state.
- 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_69d8b90aac308190801e2c57d8c5bfe5 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4de0c8aa88190b4ded7e6d05f6edf |
completed | April 19, 2026, 1:52 p.m. |
| PD | Predicate disambiguation | batch_69e43317d11c81908d1dc14921566b47 |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:29 a.m.