Triple
T9123915
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sakhalin-1 project |
E218925
|
entity |
| Predicate | developsResourceType |
P72244
|
FINISHED |
| Object | crude oil |
—
|
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: crude oil | Statement: [Sakhalin-1 project, developsResourceType, crude oil]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: developsResourceType Context triple: [Sakhalin-1 project, developsResourceType, crude oil]
-
A.
developsComponentFor
Indicates that one entity creates or builds a component intended to be used by or within another entity.
-
B.
managesResourceType
Indicates that an entity is responsible for overseeing, controlling, or administering a particular type or category of resource.
-
C.
developedProductType
chosen
Indicates that an entity (such as a project, activity, or organization) has resulted in or produced a specific type of product.
-
D.
primaryResourceType
Indicates the main or predominant type/category of resource associated with an entity or activity.
-
E.
hasDevelopmentType
Indicates the type or category of development associated with an entity, such as the nature, form, or stage of its development.
- 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_69ca83dddd548190983b96c664f7f367 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca8b5fa188190be6465e74cf26915 |
completed | April 1, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69cc66003e3c819091e1e42c9cf7c781 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:17 p.m.