Triple
T37453012
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wytch Farm oil field |
E930716
|
entity |
| Predicate | hasProductTransport |
P199174
|
FINISHED |
| Object | pipeline export |
—
|
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: pipeline export | Statement: [Wytch Farm oil field, hasProductTransport, pipeline export]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProductTransport Context triple: [Wytch Farm oil field, hasProductTransport, pipeline export]
-
A.
hasTransportCommodity
chosen
Indicates that a mode of transport carries or is used to move a specified commodity or type of goods.
-
B.
hasTransporters
Indicates that one entity possesses, provides, or is equipped with one or more means of transportation for another entity or purpose.
-
C.
hasTransportCode
Indicates that an entity is associated with a specific transport-related code used to identify or classify its mode, method, or details of transportation.
-
D.
hasTransportCategory
Indicates that one entity is classified under a particular category or type of transport associated with another entity.
-
E.
hasTransported
Indicates that one entity has carried or conveyed another entity from one location to another.
- 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_69f76ec0b9488190b7a4fae632bd1d2f |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a13a1308190a202df66f4781855 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:17 p.m.