Triple
T8933
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Truman Doctrine |
E178
|
entity |
| Predicate | ideologicalBasis |
P496
|
FINISHED |
| Object | anticommunism |
—
|
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: anticommunism | Statement: [Truman Doctrine, ideologicalBasis, anticommunism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ideologicalBasis Context triple: [Truman Doctrine, ideologicalBasis, anticommunism]
-
A.
ideology
chosen
Indicates the belief system or set of political, social, or philosophical principles that an entity adheres to or promotes.
-
B.
coreIdea
Indicates the central concept or primary message that underlies or unifies something, such as a text, argument, or work.
-
C.
foreignPolicyDoctrine
Indicates a state's overarching principles or strategic approach that guide its decisions and behavior in international relations.
-
D.
foundingDocument
Indicates that one entity serves as the official charter, constitution, or primary legal/organizational document that establishes or defines the other entity.
-
E.
legalBasis
Indicates the legal rule, authority, or justification under which an action, decision, or status is established or carried out.
- 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_69a23bb612708190b09f25385e4b63d1 |
completed | Feb. 28, 2026, 12:49 a.m. |
| NER | Named-entity recognition | batch_69a240b249788190af8dbf7e80e9c91b |
completed | Feb. 28, 2026, 1:11 a.m. |
| PD | Predicate disambiguation | batch_69a23fe52ec48190a4d24101c91434ed |
completed | Feb. 28, 2026, 1:07 a.m. |
Created at: Feb. 28, 2026, 12:54 a.m.