Triple
T134427
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Interwar period |
E2718
|
entity |
| Predicate | mainIdeology |
P496
|
FINISHED |
| Object | fascism |
—
|
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: fascism | Statement: [Interwar period, mainIdeology, fascism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainIdeology Context triple: [Interwar period, mainIdeology, fascism]
-
A.
ideology
chosen
Indicates the belief system or set of political, social, or philosophical principles that an entity adheres to or promotes.
-
B.
traditionalPoliticalAlignment
Indicates how closely an entity’s political views or affiliations align with established, historically dominant, or customary political positions within a given context.
-
C.
politicalRationale
Indicates the reasoning, justification, or strategic considerations underlying a political decision, stance, or action.
-
D.
coreIdea
Indicates the central concept or primary message that underlies or unifies something, such as a text, argument, or work.
-
E.
politicalGoal
Indicates a relationship where an entity aims to achieve, promote, or realize a specific political outcome, policy, or state of affairs.
- 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_69a2520c0f3481908b0ed054a2fca8d0 |
completed | Feb. 28, 2026, 2:25 a.m. |
| NER | Named-entity recognition | batch_69a25788b2688190a45b39447f702551 |
completed | Feb. 28, 2026, 2:48 a.m. |
| PD | Predicate disambiguation | batch_69a25650251c81908a6ea6368cd61198 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:30 a.m.