Triple
T12513532
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman Catholic Church in Cuba |
E299139
|
entity |
| Predicate | experiencedTensionPeriod |
P61198
|
FINISHED |
| Object | post-1959 revolutionary era |
—
|
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: post-1959 revolutionary era | Statement: [Roman Catholic Church in Cuba, experiencedTensionPeriod, post-1959 revolutionary era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: experiencedTensionPeriod Context triple: [Roman Catholic Church in Cuba, experiencedTensionPeriod, post-1959 revolutionary era]
-
A.
tension
Indicates a state of strain, stress, or conflict existing between entities, often involving opposing forces, interests, or emotions.
-
B.
hasTension
chosen
Indicates the presence of strain, stress, or conflict between entities in their relationship or interaction.
-
C.
tensionArea
Indicates the region or extent over which mechanical or emotional tension is distributed or experienced.
-
D.
experienceDuration
Indicates the length of time over which an entity undergoes or has undergone a particular experience or event.
-
E.
experiencedProcess
Indicates that an entity has undergone or participated in a particular process or event.
- 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_69d6ada4cd388190ae3bbf83ff87057a |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d954b867dc8190af8a70f797e4d133 |
completed | April 10, 2026, 7:51 p.m. |
| PD | Predicate disambiguation | batch_69d954096af88190b6be81b008c82139 |
completed | April 10, 2026, 7:48 p.m. |
Created at: April 8, 2026, 9:57 p.m.