Triple
T34644568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LERU-CE7 group (continental partners) |
E889658
|
entity |
| Predicate | collaborationWithLERU |
P26572
|
FINISHED |
| Object | policy development |
—
|
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: policy development | Statement: [LERU-CE7 group (continental partners), collaborationWithLERU, policy development]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collaborationWithLERU Context triple: [LERU-CE7 group (continental partners), collaborationWithLERU, policy development]
-
A.
collaborationOf
Indicates a relationship in which two or more entities work together jointly toward a shared goal or outcome.
-
B.
collaborationArea
chosen
Indicates the domain, topic, or field in which two or more entities work together or collaborate.
-
C.
collaborationRegion
Indicates the geographic or administrative area within which the collaboration between entities takes place or is defined.
-
D.
establishedInCollaborationWith
Indicates that something was created, founded, or set up jointly through cooperative effort between two or more parties.
-
E.
implementedInCooperationWith
Indicates that an action, project, or initiative was carried out jointly or collaboratively together with another party.
- 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_69f349d825c88190bfc6170ac9281260 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f72294d07081908744e2cf9b5fbd91 |
completed | May 3, 2026, 10:25 a.m. |
| PD | Predicate disambiguation | batch_69f72157af108190880317a62e634bb0 |
completed | May 3, 2026, 10:20 a.m. |
Created at: May 1, 2026, 2:04 a.m.