Triple
T8097505
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thames oil terminals |
E189022
|
entity |
| Predicate | handlesProduct |
P3585
|
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: [Thames oil terminals, handlesProduct, crude oil]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: handlesProduct Context triple: [Thames oil terminals, handlesProduct, crude oil]
-
A.
hasProduct
chosen
Indicates that an entity possesses, offers, or is associated with a particular product.
-
B.
exportProduct
Indicates that an entity sends or sells a product from its own country or region to another country or external market.
-
C.
ensuresWellDefinedProductBy
Indicates that one entity guarantees the resulting product or outcome of another entity is well-defined, consistent, and unambiguous.
-
D.
productDomain
Indicates the domain, field, or area of application to which a given product belongs or is relevant.
-
E.
givesProductRepresentationOf
Indicates that one entity provides or expresses another entity in the form of a product representation, such as a model, depiction, or structured description of that product.
- 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_69ca82b886d88190a9cba0d5a4a27521 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb4294b73481908c8373b8eca0f608 |
completed | March 31, 2026, 3:42 a.m. |
| PD | Predicate disambiguation | batch_69cb04a14cd88190a79ed26cbeec1c33 |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:30 p.m.