Triple
T27638281
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Europe à plusieurs vitesses |
E696521
|
entity |
| Predicate | soutenuPour |
P1853
|
FINISHED |
| Object | flexibilité institutionnelle |
—
|
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: flexibilité institutionnelle | Statement: [Europe à plusieurs vitesses, soutenuPour, flexibilité institutionnelle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: soutenuPour Context triple: [Europe à plusieurs vitesses, soutenuPour, flexibilité institutionnelle]
-
A.
supportAgainst
Indicates providing help, resources, or advocacy to oppose or resist a particular target, threat, or adversary.
-
B.
supportedSide
Indicates that one entity backed, favored, or provided assistance to a particular side or party in a conflict, dispute, or competition.
-
C.
support
chosen
Indicates that one entity provides assistance, endorsement, or backing to another entity or its actions.
-
D.
supportedCouncil
Indicates that an entity provided backing, endorsement, or assistance to a council.
-
E.
sustainedBy
Indicates that one entity is maintained, supported, or kept in existence by another entity over a period of time.
- 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_69ef5909f3848190805f35b76833e722 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f6318e4c9c8190960df19eed7546fa |
completed | May 2, 2026, 5:17 p.m. |
| PD | Predicate disambiguation | batch_69f62c1921008190a62675a31f66a875 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 2:25 p.m.