Triple
T33564215
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European Communities pillar |
E859710
|
entity |
| Predicate | coveredPolicyArea |
P5037
|
FINISHED |
| Object | internal market |
—
|
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: internal market | Statement: [European Communities pillar, coveredPolicyArea, internal market]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coveredPolicyArea Context triple: [European Communities pillar, coveredPolicyArea, internal market]
-
A.
coversPolicyArea
chosen
Indicates that a policy, document, or initiative includes or addresses a particular policy area or topic within its scope.
-
B.
coordinatesPolicyAreas
Indicates that one entity organizes and aligns activities or strategies across multiple policy areas involving another entity.
-
C.
commonPolicyArea
Indicates that two entities share the same policy domain, topic, or area of regulatory or legislative focus.
-
D.
hasPolicyArea
Indicates that an entity (such as a policy, program, or initiative) is associated with or pertains to a specific policy area or domain.
-
E.
policyAreaScope
Indicates the specific policy domain or thematic area to which an action, decision, or measure is relevant or applies.
- 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_69f3497c1d288190a844ea699914e038 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fbbc49da8c8190902bbb05d2477cab |
completed | May 6, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69fbb13f34b08190bbbb220ac1e6e666 |
completed | May 6, 2026, 9:23 p.m. |
Created at: May 1, 2026, 1:40 a.m.