Triple
T2823389
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Claude McKay |
E54861
|
entity |
| Predicate | formerIdeology |
P496
|
FINISHED |
| Object | communism |
—
|
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: communism | Statement: [Claude McKay, formerIdeology, communism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerIdeology Context triple: [Claude McKay, formerIdeology, communism]
-
A.
ideology
chosen
Indicates the belief system or set of political, social, or philosophical principles that an entity adheres to or promotes.
-
B.
opposingIdeology
Indicates that two entities hold conflicting or mutually incompatible belief systems, doctrines, or ideological positions.
-
C.
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.
-
D.
mainIdeologue
Indicates that one entity serves as the primary theorist or chief ideological architect behind another entity’s beliefs, policies, or movement.
-
E.
ideologicalFamilies
Indicates that two or more entities are grouped or related based on sharing the same or closely aligned ideological traditions or belief systems.
- 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_69ab49e100c0819082a40cb797383243 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abdf15b7288190a03d1193cc0544a6 |
completed | March 7, 2026, 8:17 a.m. |
| PD | Predicate disambiguation | batch_69abdd08f2f481908c3da8a9c7a00552 |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 9:59 p.m.