Triple
T2907461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Contra Costa Canal |
E63599
|
entity |
| Predicate | intakeLocation |
P42668
|
FINISHED |
| Object | near Oakley, California |
—
|
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: near Oakley, California | Statement: [Contra Costa Canal, intakeLocation, near Oakley, California]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intakeLocation Context triple: [Contra Costa Canal, intakeLocation, near Oakley, California]
-
A.
airIntakeLocation
Indicates the physical position or area where air is drawn into a system, device, or structure.
-
B.
airIntakeType
Indicates the type or configuration of the system or mechanism used to draw air into an engine or device.
-
C.
locatedAtOutletOf
Indicates that one entity is positioned at or directly adjacent to the outlet or discharge point of another entity (such as a flow, channel, or system).
-
D.
mouthOf
Indicates the location where one entity (typically a river or similar feature) empties into or opens out into another, larger body or feature.
-
E.
portLocation
Indicates that a port is geographically situated at or associated with a specific location.
- F. None of above. chosen
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_69ab4c44ab448190b9411324e8a1fc1d |
completed | March 6, 2026, 9:51 p.m. |
| NER | Named-entity recognition | batch_69abe0d0628c81909680af2f0db2ecae |
completed | March 7, 2026, 8:24 a.m. |
| PD | Predicate disambiguation | batch_69abdd19bac881908f047d616aca8438 |
completed | March 7, 2026, 8:08 a.m. |
| PDg | Predicate description generation | batch_69abdd96670c8190b727f9ac27dadf67 |
completed | March 7, 2026, 8:11 a.m. |
Created at: March 6, 2026, 10:11 p.m.