Triple
T5044273
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Single European Act |
E113621
|
entity |
| Predicate | expandedCompetenceIn |
P18508
|
FINISHED |
| Object | environmental policy |
—
|
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: environmental policy | Statement: [Single European Act, expandedCompetenceIn, environmental policy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expandedCompetenceIn Context triple: [Single European Act, expandedCompetenceIn, environmental policy]
-
A.
definesCompetenceOf
Indicates that one entity specifies, determines, or establishes the scope, level, or nature of another entity’s competence or capability.
-
B.
competenceArea
chosen
Indicates that one entity has a particular domain, field, or area in which it possesses competence, expertise, or responsibility.
-
C.
competence
Indicates that an entity has the ability, skill, or qualification to perform a task or fulfill a role effectively.
-
D.
hasCompetence
Indicates that an entity possesses the ability, skill, or qualification to perform a specific task or function effectively.
-
E.
expandedBy
Indicates that one entity increases, elaborates, or builds upon the scope, detail, or extent 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_69bd44391fc48190a311ce9c826c209b |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd73fc04f08190aba851fa0192d0fb |
completed | March 20, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69bd71529d608190a53470ba6c14bb1d |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:37 p.m.