Triple
T7470794
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Agir |
E176497
|
entity |
| Predicate | stanceOnEurope |
P20042
|
FINISHED |
| Object | pro-European |
—
|
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 | Statement: [Agir, stanceOnEurope, pro-European]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stanceOnEurope Context triple: [Agir, stanceOnEurope, pro-European]
-
A.
positionOnEuropeanIntegration
chosen
Indicates a stance or viewpoint an entity holds regarding the process, policies, or degree of European integration.
-
B.
politicalPositionOnEuropeanUnion
Indicates a stance or viewpoint that an entity holds regarding the policies, membership, or role of the European Union.
-
C.
roleInEurope
Indicates that an entity holds a specific function, position, or responsibility within a European context, such as within Europe as a region or its institutions.
-
D.
EuropeanAffiliation
Indicates that an entity is associated with Europe, such as by membership, origin, operation, or jurisdiction within European countries or institutions.
-
E.
EUMemberState
Indicates that an entity is a country that is a member state of 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_69c69f223fd88190b4c69b95d7cbeeda |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f4145d608190bd93239f04f7da41 |
completed | March 27, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69c6f03d967081908a8e696ff9693b90 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:41 p.m.