Triple
T287932
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Open VLD |
E5925
|
entity |
| Predicate | politicalSpectrum |
P7253
|
FINISHED |
| Object | liberal |
—
|
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: liberal | Statement: [Open VLD, politicalSpectrum, liberal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: politicalSpectrum Context triple: [Open VLD, politicalSpectrum, liberal]
-
A.
politicalSpectrumPosition
chosen
Indicates the relative ideological placement of an entity along a political spectrum (e.g., left–right, liberal–conservative).
-
B.
politicalPattern
Indicates a recurring or characteristic way in which political behaviors, decisions, or power dynamics are organized or expressed.
-
C.
traditionalPoliticalAlignment
Indicates how closely an entity’s political views or affiliations align with established, historically dominant, or customary political positions within a given context.
-
D.
politicalParty
Indicates that an entity is affiliated with, belongs to, or is a member of a specific political party.
-
E.
politicalRationale
Indicates the reasoning, justification, or strategic considerations underlying a political decision, stance, or action.
- 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_69a25946a7ac8190a78871c210213272 |
completed | Feb. 28, 2026, 2:56 a.m. |
| NER | Named-entity recognition | batch_69a25e2f5c0081908e548b314f5e986d |
completed | Feb. 28, 2026, 3:17 a.m. |
| PD | Predicate disambiguation | batch_69a25b7c1448819082064f474633acd5 |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 3:02 a.m.