Triple
T28950278
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tatiana Navka / Roman Kostomarov |
E730992
|
entity |
| Predicate | partnershipBegan |
P63015
|
FINISHED |
| Object | 1998 |
—
|
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: 1998 | Statement: [Tatiana Navka / Roman Kostomarov, partnershipBegan, 1998]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partnershipBegan Context triple: [Tatiana Navka / Roman Kostomarov, partnershipBegan, 1998]
-
A.
partnerStartDate
chosen
Indicates the date on which the partnership or partner relationship between the entities begins.
-
B.
formedAsPartnershipBetween
Indicates that something was created or established through a formal partnership between two or more entities.
-
C.
endedPartnershipWith
Indicates that a previously existing partnership or collaborative relationship between two entities has been terminated.
-
D.
cooperationEstablished
Indicates that a cooperative relationship or partnership has been formally initiated and recognized between the involved entities.
-
E.
cooperationPartner
Indicates that two entities are engaged in a collaborative relationship, working together toward shared goals or mutual benefit.
- 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_69f043eb9bcc819091ac7b07aecb6475 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f69383222c81909d8baa04129d5c81 |
completed | May 3, 2026, 12:14 a.m. |
| PD | Predicate disambiguation | batch_69f690eb1e948190aab41a89969519a5 |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 28, 2026, 8:43 a.m.