Triple
T26670518
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adriatic-Ionian region |
E672317
|
entity |
| Predicate | hasPolicyPillar |
P176742
|
FINISHED |
| Object | blue growth |
—
|
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: blue growth | Statement: [Adriatic-Ionian region, hasPolicyPillar, blue growth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPolicyPillar Context triple: [Adriatic-Ionian region, hasPolicyPillar, blue growth]
-
A.
hasPolicySupport
Indicates that one entity provides endorsement, backing, or approval for a specific policy associated with another entity.
-
B.
hasPolicyArea
Indicates that an entity (such as a policy, program, or initiative) is associated with or pertains to a specific policy area or domain.
-
C.
hasPolicyGoal
Indicates that an entity is associated with, or aims to achieve, a specific policy objective or target.
-
D.
policyPillar
chosen
Indicates that something (such as a program, measure, or objective) belongs to, supports, or is categorized under a particular policy pillar within a broader policy framework.
-
E.
hasPolicyInterestOf
Indicates that one entity holds or is associated with a specific policy interest belonging to or concerning 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_69eecda00a9c8190b2691f4d89db03b6 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f7431c0eec81909ead443e07d75e18 |
completed | May 3, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69f74143cf708190a12d487884298437 |
completed | May 3, 2026, 12:36 p.m. |
Created at: April 27, 2026, 3:12 a.m.