Triple
T36167477
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mazatlán–Matamoros corridor |
E1046048
|
entity |
| Predicate | coastConnected |
P130358
|
FINISHED |
| Object | Pacific coast of Mexico |
—
|
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: Pacific coast of Mexico | Statement: [Mazatlán–Matamoros corridor, coastConnected, Pacific coast of Mexico]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coastConnected Context triple: [Mazatlán–Matamoros corridor, coastConnected, Pacific coast of Mexico]
-
A.
connectsCoastToBorder
Indicates a relationship where something (such as a route, feature, or boundary) links a coastal area directly to a national or regional border.
-
B.
connectsToCoastAt
Indicates that one entity has a direct physical or geographical connection or access to a coastline at the location of another entity.
-
C.
coastlineAssociation
chosen
Indicates an association between an entity and a coastline, such as adjacency, alignment, or functional connection to that coastal boundary.
-
D.
includesCoastOf
Indicates that one geographic or administrative entity encompasses or contains the coastline of another entity.
-
E.
areCoastal
Indicates that the entities are located on or adjacent to a coastline or seashore.
- 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_69f76e396bc88190b99d221bff9be27a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b69b333081909cadbed3fcb8ecf5 |
completed | May 3, 2026, 8:56 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c2a5f8819094ad4621d7b97e0c |
completed | May 3, 2026, 8:49 p.m. |
Created at: May 3, 2026, 4:08 p.m.