Triple
T32473436
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Iranian Oil Company |
E829904
|
entity |
| Predicate | exportPartner |
P40409
|
FINISHED |
| Object | Asian oil markets |
—
|
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: Asian oil markets | Statement: [National Iranian Oil Company, exportPartner, Asian oil markets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exportPartner Context triple: [National Iranian Oil Company, exportPartner, Asian oil markets]
-
A.
exportPartners
chosen
Indicates a relationship where one entity collaborates with or serves as a partner to another in exporting goods or services across borders.
-
B.
cooperationPartner
Indicates that two entities are engaged in a collaborative relationship, working together toward shared goals or mutual benefit.
-
C.
selectedPartner
Indicates that one entity has been chosen or designated as the partner of another entity.
-
D.
coalitionPartnerWith
Indicates that two entities are formally aligned in a cooperative coalition, sharing goals or actions as partners within that coalition.
-
E.
coreModulePartner
Indicates that one entity serves as a primary or foundational partner module in relation to another module.
- 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_69f3491ee87c81908cbf5890079c2af6 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c35761fc8190a32a7ff34fc86b52 |
completed | May 3, 2026, 3:39 a.m. |
| PD | Predicate disambiguation | batch_69f6bd25bed08190befcabd3a41ffadf |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 12:57 a.m.