Triple
T22784375
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Katow |
E563924
|
entity |
| Predicate | ideologicalCommitment |
P6760
|
FINISHED |
| Object | revolutionary cause |
—
|
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: revolutionary cause | Statement: [Katow, ideologicalCommitment, revolutionary cause]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ideologicalCommitment Context triple: [Katow, ideologicalCommitment, revolutionary cause]
-
A.
ideologicalEmphasis
Indicates a relationship where an entity places particular focus or priority on a specific ideology or set of ideological principles.
-
B.
ideologicalCore
Indicates that one entity represents the central or foundational set of beliefs, values, or principles that fundamentally shape and guide another entity’s ideology.
-
C.
ideologicalGoal
chosen
Indicates that an entity aims to promote, realize, or advance a particular ideology or set of ideological principles.
-
D.
ideologicalInfluence
Indicates that one entity’s beliefs, values, or doctrines shape, guide, or significantly affect the ideology of another entity.
-
E.
ideologicalUse
Indicates that something is employed to promote, support, or express a particular ideology or set of beliefs.
- 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_69e2455500788190b4b33030461f3bbd |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17c2f9ba48190996b4c3926728c03 |
completed | April 29, 2026, 3:34 a.m. |
| PD | Predicate disambiguation | batch_69eed2c32e8c8190b73bb9965ed47d64 |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:29 p.m.