Triple
T19722654
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quod Apostolici Muneris |
E473648
|
entity |
| Predicate | condemnsAsThreatTo |
P42780
|
FINISHED |
| Object | Christian society |
—
|
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: Christian society | Statement: [Quod Apostolici Muneris, condemnsAsThreatTo, Christian society]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: condemnsAsThreatTo Context triple: [Quod Apostolici Muneris, condemnsAsThreatTo, Christian society]
-
A.
threatensToDestroy
Indicates that one entity has expressed an intention or warning that it will cause the complete ruin or elimination of another entity or object.
-
B.
threatenedBy
Indicates that one entity poses a danger or potential harm to another entity.
-
C.
threatToRuleOf
Indicates a relationship where one entity poses a danger or challenge to the authority, control, or governance exercised by another entity.
-
D.
aimOfCondemnation
chosen
Indicates that an act of condemnation is directed toward a particular target or objective.
-
E.
condemnedAs
Indicates that one entity formally or strongly denounces another entity by labeling it as wrong, guilty, or unacceptable.
- 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_69d8e517ebd48190979ee76723bcfadf |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e649f587d88190bf519fec7ce634d3 |
completed | April 20, 2026, 3:44 p.m. |
| PD | Predicate disambiguation | batch_69e5304a7aac8190ac13f75f0c008e45 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:46 p.m.