Triple
T30581737
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Transneft pipeline system |
E778401
|
entity |
| Predicate | managingCompanyInstanceOf |
P181671
|
FINISHED |
| Object | state-owned enterprise |
—
|
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: state-owned enterprise | Statement: [Transneft pipeline system, managingCompanyInstanceOf, state-owned enterprise]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: managingCompanyInstanceOf Context triple: [Transneft pipeline system, managingCompanyInstanceOf, state-owned enterprise]
-
A.
managementCompany
Indicates that one entity serves as the managing company responsible for overseeing or administering another entity.
-
B.
governingCompany
Indicates that one company exercises control, authority, or management over another company.
-
C.
memberCompany
Indicates that a company is formally part of, or affiliated as a member with, a larger organization, group, or association.
-
D.
parentCompanyOfTenants
Indicates that one company serves as the parent or owning company of one or more tenant entities.
-
E.
ownedCompany
Indicates that one entity possesses legal ownership or controlling interest in another entity that is a company.
- 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_69f224a04b248190b0ca443ec86207b8 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7805ce6208190ac6dbd9c97989978 |
completed | May 3, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_69f77956ec648190ba4fb7e9d83fd107 |
completed | May 3, 2026, 4:35 p.m. |
| PDg | Predicate description generation | batch_69f7805c25dc8190b9977c561ba15975 |
completed | May 3, 2026, 5:05 p.m. |
Created at: April 29, 2026, 8:23 p.m.