Triple
T27341917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barents region |
E684127
|
entity |
| Predicate | cooperationEstablished |
P162198
|
FINISHED |
| Object | 1993 |
—
|
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: 1993 | Statement: [Barents region, cooperationEstablished, 1993]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cooperationEstablished Context triple: [Barents region, cooperationEstablished, 1993]
-
A.
definesCooperationWith
Indicates that one entity formally specifies or establishes the terms, scope, or nature of cooperative interaction with another entity.
-
B.
cooperationAmong
Indicates a relationship in which multiple entities work together collaboratively toward shared goals or mutual benefit.
-
C.
cooperationContext
Indicates the situational or environmental conditions under which two or more entities are cooperating or collaborating.
-
D.
cooperationType
Indicates the specific kind or form of cooperative relationship that exists between the related entities.
-
E.
establishedInCollaborationWith
Indicates that something was created, founded, or set up jointly through cooperative effort between two or more parties.
- F. None of above. chosen
Provenance (4 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_69ef1480a76481908684256ddd5bfda3 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f62b9e5ba88190a3c0d46edec7afe7 |
completed | May 2, 2026, 4:51 p.m. |
| PD | Predicate disambiguation | batch_69f620e4b1c88190a17940251abc68fd |
completed | May 2, 2026, 4:05 p.m. |
| PDg | Predicate description generation | batch_69f621fbfc2c8190bfa802d7dc0f6aa4 |
completed | May 2, 2026, 4:10 p.m. |
Created at: April 27, 2026, 11:43 a.m.