Triple
T18870317
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Freedom and Solidarity |
E461549
|
entity |
| Predicate | europeanPolicy |
P20039
|
FINISHED |
| Object | pro-European Union |
—
|
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: pro-European Union | Statement: [Freedom and Solidarity, europeanPolicy, pro-European Union]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: europeanPolicy Context triple: [Freedom and Solidarity, europeanPolicy, pro-European Union]
-
A.
positionOnEuropeanIntegration
Indicates a stance or viewpoint an entity holds regarding the process, policies, or degree of European integration.
-
B.
politicalPositionOnEuropeanUnion
chosen
Indicates a stance or viewpoint that an entity holds regarding the policies, membership, or role of the European Union.
-
C.
euroParticipation
Indicates that an entity takes part in or is involved with the Euro currency system or Eurozone monetary framework.
-
D.
statusInCouncilOfEurope
Indicates the relationship between an entity and its membership or participation status within the Council of Europe.
-
E.
europeanUnionStatus
Indicates whether an entity is a member of, associated with, or otherwise holds a defined status in relation to the European Union.
- 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_69d8dcfb7b9c8190854e7b171b98ea2e |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c2a8c8208190a3d709e96ebe184f |
completed | April 20, 2026, 6:07 a.m. |
| PD | Predicate disambiguation | batch_69e48d2166b88190add38de96cedc65c |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:57 a.m.