Triple
T29180914
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Consolations |
E739741
|
entity |
| Predicate | containsReligiousInfluence |
P196695
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Consolations, containsReligiousInfluence, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsReligiousInfluence Context triple: [Consolations, containsReligiousInfluence, true]
-
A.
laterInfluencedByReligion
Indicates that an entity was influenced at a later time by a particular religion or religious tradition.
-
B.
influencedReligion
Indicates that one entity has had a shaping or modifying effect on the religious beliefs, practices, or traditions of another entity.
-
C.
influencedByReligion
Indicates that an entity’s characteristics, decisions, or development are shaped or affected by religious beliefs, practices, or institutions.
-
D.
hasEcclesiasticalInfluenceIn
Indicates that an entity holds religious or church-related authority, impact, or sway within a specified region, institution, or context.
-
E.
doctrinalInfluenceOn
Indicates that one doctrine has influenced, shaped, or contributed to the development of another doctrine.
- 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_69f07cb74c2c8190ad396487fcb4fde6 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69fe629b4fa481908467c7c41b77f0c6 |
completed | May 8, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_69fe61bb260c819083f9378a3a06ca47 |
completed | May 8, 2026, 10:20 p.m. |
| PDg | Predicate description generation | batch_69fe629a8d4c8190b4aa4dee39efc0a6 |
completed | May 8, 2026, 10:24 p.m. |
Created at: April 28, 2026, 11:57 a.m.