Triple
T36923801
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monçada |
E913278
|
entity |
| Predicate | themeInBackstory |
P186696
|
FINISHED |
| Object | religious persecution |
—
|
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 | Statement: [Monçada, themeInBackstory, religious persecution]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: themeInBackstory Context triple: [Monçada, themeInBackstory, religious persecution]
-
A.
themeChange
Indicates that an entity undergoes a change in its theme, style, or subject, typically transitioning from one thematic state or configuration to another.
-
B.
themeFor
Indicates that something serves as the central subject, topic, or focus for another thing (such as an event, work, or activity).
-
C.
theme
Indicates the entity that is the primary participant or content affected or characterized by an action, event, or state.
-
D.
themeInArc
Indicates that something serves as a central theme or recurring subject within a particular narrative arc.
-
E.
transformationTheme
Indicates a thematic relationship in which one entity centers on or explores the process, experience, or idea of transformation in another.
- F. None of above. chosen
Provenance (4 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_69f76e885b848190bad82c87e9525486 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f9fe1a1ca4819084c196f0041f0be2 |
completed | May 5, 2026, 2:26 p.m. |
| PD | Predicate disambiguation | batch_69f7cf79ddb08190a083405cccc14137 |
completed | May 3, 2026, 10:43 p.m. |
| PDg | Predicate description generation | batch_69f9fd66eed48190bdc26a8def328c2d |
completed | May 5, 2026, 2:23 p.m. |
Created at: May 3, 2026, 4:13 p.m.