Triple
T34504937
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raxaul |
E885855
|
entity |
| Predicate | hasPetroleumTransport |
P175212
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Raxaul, hasPetroleumTransport, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPetroleumTransport Context triple: [Raxaul, hasPetroleumTransport, yes]
-
A.
hasOilTerminal
Indicates that one entity possesses, hosts, or contains an oil terminal used for storing or transferring oil.
-
B.
hasPetrochemicalPipelines
chosen
Indicates that one entity possesses, controls, or is associated with petrochemical pipelines connecting it to other locations or facilities.
-
C.
hasTransporters
Indicates that one entity possesses, provides, or is equipped with one or more means of transportation for another entity or purpose.
-
D.
hasTransportationSystem
Indicates that an entity possesses, operates, or is served by an organized system for transporting people or goods.
-
E.
hasGroundTransportation
Indicates that an entity provides, includes, or is connected to transportation services or options that operate on land (e.g., cars, buses, trains).
- 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_69f349cc0220819081f154c6964f4dc2 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fe066d62b48190867df334039be786 |
completed | May 8, 2026, 3:51 p.m. |
| PD | Predicate disambiguation | batch_69fe03afde3c8190a5b9b0778d19eb1a |
completed | May 8, 2026, 3:39 p.m. |
Created at: May 1, 2026, 2:01 a.m.