Triple
T23396700
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European Economic Area |
E559378
|
entity |
| Predicate | policyScopeIncludes |
P14568
|
FINISHED |
| Object | competition rules |
—
|
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: competition rules | Statement: [European Economic Area, policyScopeIncludes, competition rules]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: policyScopeIncludes Context triple: [European Economic Area, policyScopeIncludes, competition rules]
-
A.
organizationalScope
Indicates the range or extent of responsibility, authority, or applicability that an action, policy, or relationship has within an organization or its sub-units.
-
B.
scopeOfUse
Indicates the range, context, or conditions under which something is intended, allowed, or applicable to be used.
-
C.
availabilityScope
Indicates the extent or context within which something is available, accessible, or applicable.
-
D.
scopeType
Indicates the specific range, level, or context within which a given relationship, rule, or action is defined or applies.
-
E.
coverageScope
chosen
Indicates the extent or range of entities, conditions, or situations that are included under a particular coverage or applicability.
- 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_69e24549610c8190a069d6411ce5f661 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1a4dc48008190bdcf92f8d9a5232d |
completed | April 29, 2026, 6:27 a.m. |
| PD | Predicate disambiguation | batch_69f061dde2e481908308952f9c0d3c2e |
completed | April 28, 2026, 7:29 a.m. |
Created at: April 17, 2026, 5:37 p.m.