Triple
T35537769
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kern River Pipeline |
E1026975
|
entity |
| Predicate | primaryDestinationMarket |
P142461
|
FINISHED |
| Object | California |
E1909002
|
NE 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: California | Statement: [Kern River Pipeline, primaryDestinationMarket, California]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryDestinationMarket Context triple: [Kern River Pipeline, primaryDestinationMarket, California]
-
A.
primaryTargetCountry
Indicates the country that is the main or principal focus or destination of the related action, plan, or effect.
-
B.
primaryDomesticDestination
chosen
Indicates that one location is the main or most significant destination within the same country for travel, transport, or activity originating from another location.
-
C.
primaryDestinationsType
Indicates the type or category of main destinations associated with an entity or activity.
-
D.
primaryFreightDestination
Indicates the main location to which freight is intended to be shipped or delivered.
-
E.
primaryCountryServed
Indicates the main country that is primarily served or targeted by an entity’s activities, services, or operations.
- F. None of above.
Provenance (4 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_69f76dff7e508190b28ceeee770dce23 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3852e9b2f481908ddf999b98bdf356 |
completed | June 21, 2026, 9:08 p.m. |
| PD | Predicate disambiguation | batch_6a037a04d8348190a4819666eab42c9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:04 p.m.