Triple
T7097029
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ecclesiam a Jesu Christo |
E165354
|
entity |
| Predicate | condemnsAs |
P21724
|
FINISHED |
| Object | impious associations |
—
|
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: impious associations | Statement: [Ecclesiam a Jesu Christo, condemnsAs, impious associations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: condemnsAs Context triple: [Ecclesiam a Jesu Christo, condemnsAs, impious associations]
-
A.
condemnedAs
chosen
Indicates that one entity formally or strongly denounces another entity by labeling it as wrong, guilty, or unacceptable.
-
B.
condemnedBy
Indicates that an entity is judged, denounced, or declared wrong or unacceptable by another entity.
-
C.
condemnation
Indicates that an entity expresses strong disapproval or denunciation of another entity, action, or situation.
-
D.
condemnedIn
Indicates that an entity was formally denounced, sentenced, or declared guilty within a particular place, context, or proceeding.
-
E.
subjectOfCondemnation
Indicates that one entity is the target or object of formal disapproval, criticism, or denunciation by another entity.
- 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_69c6887e8c10819091cee237560d32da |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e5561dd08190be6b784754a0c1bc |
completed | March 27, 2026, 8:15 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c313e481908b61a23fc89f9332 |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:41 p.m.