Triple
T34864653
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Euroregions |
E1004977
|
entity |
| Predicate | mayUseFramework |
P9089
|
FINISHED |
| Object | European Grouping of Territorial Cooperation |
—
|
NE NERFINISHED |
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: European Grouping of Territorial Cooperation | Statement: [Euroregions, mayUseFramework, European Grouping of Territorial Cooperation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayUseFramework Context triple: [Euroregions, mayUseFramework, European Grouping of Territorial Cooperation]
-
A.
mayAllowUse
Indicates that one entity has the potential or permission to allow another entity to use or access something.
-
B.
mayUseProtocol
Indicates that an entity is permitted or authorized to employ a specified protocol for communication or operation.
-
C.
appliesFramework
chosen
Indicates that one entity uses or implements a particular framework in relation to another entity or context.
-
D.
canUse
Indicates that one entity has the ability, permission, or suitability to make use of another entity or resource.
-
E.
frameworkFor
Indicates that one entity serves as a supporting structure, system, or basis that organizes, guides, or enables the development or functioning of another entity.
- 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_69f76dbb678081909a247b9b5e1a73ac |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f782f4f10081908f97f6d0d2dbeec7 |
completed | May 3, 2026, 5:16 p.m. |
| PD | Predicate disambiguation | batch_69f780ff71cc8190a67e71076fbad81a |
completed | May 3, 2026, 5:08 p.m. |
Created at: May 3, 2026, 4 p.m.