Triple
T2080166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ASEA-UNINET |
E45219
|
entity |
| Predicate | cooperationBetween |
P21905
|
FINISHED |
| Object | European universities |
—
|
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: European universities | Statement: [ASEA-UNINET, cooperationBetween, European universities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cooperationBetween Context triple: [ASEA-UNINET, cooperationBetween, European universities]
-
A.
cooperationType
Indicates the specific kind or form of cooperative relationship that exists between the related entities.
-
B.
cooperatingState
Indicates that one state collaborates or works jointly with another state toward shared goals or activities.
-
C.
coOperator
chosen
Indicates that two or more entities work together as partners or collaborators in performing an activity or achieving a shared objective.
-
D.
coordinatedWith
Indicates that two or more entities have worked together in an organized, cooperative manner toward a shared task, goal, or activity.
-
E.
coalitionPartnerWith
Indicates that two entities are formally aligned in a cooperative coalition, sharing goals or actions as partners within that coalition.
- 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_69a8891869c88190a02643e3bb746f59 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abba345be48190a1895f388e7749e5 |
completed | March 7, 2026, 5:40 a.m. |
| PD | Predicate disambiguation | batch_69abb7b298a48190b4bdf7c9800b058d |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:41 p.m.