Triple
T4390908
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eastern Partnership countries |
E99358
|
entity |
| Predicate | policyInstrumentType |
P1652
|
FINISHED |
| Object | neighbourhood policy instrument |
—
|
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: neighbourhood policy instrument | Statement: [Eastern Partnership countries, policyInstrumentType, neighbourhood policy instrument]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: policyInstrumentType Context triple: [Eastern Partnership countries, policyInstrumentType, neighbourhood policy instrument]
-
A.
policyName
Indicates the specific name or title assigned to a policy associated with an entity.
-
B.
policyTool
chosen
Indicates that an entity is a tool, mechanism, or instrument used to design, implement, or enforce a policy.
-
C.
policyCharacteristic
Indicates that a policy possesses a particular attribute, feature, or quality that characterizes how it is defined or operates.
-
D.
policyLevel
Indicates the degree or tier of strictness, scope, or priority associated with a given policy.
-
E.
typeOfLegislation
Indicates the specific category or kind of legislation that a given legal act or measure belongs to.
- 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_69b3454f739481909ff6c28331f0c0b9 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b352843d7c8190929b94c94eaa63df |
completed | March 12, 2026, 11:55 p.m. |
| PD | Predicate disambiguation | batch_69b34f572efc8190bad1e5078cbcb75a |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:19 p.m.