Triple
T10165492
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A Theology of Liberation |
E235194
|
entity |
| Predicate | viewsLiberationAs |
P22619
|
FINISHED |
| Object | integral liberation |
—
|
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: integral liberation | Statement: [A Theology of Liberation, viewsLiberationAs, integral liberation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: viewsLiberationAs Context triple: [A Theology of Liberation, viewsLiberationAs, integral liberation]
-
A.
viewOnLiberation
chosen
Indicates a stance, opinion, or perspective that an entity holds regarding the concept, process, or outcomes of liberation.
-
B.
viewOnLiberty
Indicates a person's stance, opinion, or perspective regarding the concept or principles of liberty.
-
C.
definesLiberationAs
Indicates that one entity characterizes or specifies the meaning, nature, or conditions of liberation in terms of another entity or concept.
-
D.
viewsJihadAs
Indicates that one entity regards or interprets jihad in a particular way (e.g., as a concept, duty, struggle, or cause).
-
E.
liberationEvent
Indicates an event in which an entity is freed from control, confinement, or oppression by another entity or condition.
- 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_69ca84ceafd0819085828600e11bed6b |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdec6cf27481909f38839452ac0e37 |
completed | April 2, 2026, 4:11 a.m. |
| PD | Predicate disambiguation | batch_69cd4ba795808190acc9124c98c6e40f |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9:10 p.m.