Triple
T28969473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States–Mexico maritime boundary (Pacific Ocean) |
E734230
|
entity |
| Predicate | hasBorderStateOnUSSide |
P43351
|
FINISHED |
| Object | California |
—
|
NE NERFINISHED |
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: [United States–Mexico maritime boundary (Pacific Ocean), hasBorderStateOnUSSide, California]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBorderStateOnUSSide Context triple: [United States–Mexico maritime boundary (Pacific Ocean), hasBorderStateOnUSSide, California]
-
A.
borderStateOnUSSide
chosen
Indicates that a state is located on the U.S. side of an international border shared with another country.
-
B.
hasBorderWithinCountry
Indicates that one region or area shares an internal boundary with another region or area within the same country.
-
C.
hasBorderLengthWithUSA
Indicates that the length of the land or maritime border shared between a given country or region and the USA has a specified measurement.
-
D.
borderStateOf
Indicates that one state shares a common boundary or border with another state.
-
E.
hasBorderMeetingCountry
Indicates that one country shares a land or maritime border with another country.
- 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_69f05b0d1e7c819092baab93d3fe277e |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f7979a073881909a4fde2558e6b6f3 |
completed | May 3, 2026, 6:44 p.m. |
| PD | Predicate disambiguation | batch_69f7961550f88190b7bb8a9155458b54 |
completed | May 3, 2026, 6:38 p.m. |
Created at: April 28, 2026, 9:04 a.m.