Triple
T16951734
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Melchor de Mencos |
E411194
|
entity |
| Predicate | borderDirectionFromBelize |
P27801
|
FINISHED |
| Object | west |
—
|
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: west | Statement: [Melchor de Mencos, borderDirectionFromBelize, west]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderDirectionFromBelize Context triple: [Melchor de Mencos, borderDirectionFromBelize, west]
-
A.
borderDirectionFromUS
Indicates the compass direction in which a country or region lies relative to the United States along their shared border.
-
B.
borderDirectionFromCapital
Indicates the compass direction from a country's capital city to a specified border or neighboring entity.
-
C.
borderTownGuatemala
Indicates that a town is located on or near the national border of Guatemala, functioning as a border town relative to that country.
-
D.
countryBorderDirection
chosen
Indicates the cardinal or relative direction in which one country lies in relation to the border it shares with another country.
-
E.
borderCountrySide
Indicates that one country shares a land border with the side or region of 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_69d886c9c9d481909afe222093641cae |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d0197f308190af7185fc9cc7a6e9 |
completed | April 18, 2026, 6:40 p.m. |
| PD | Predicate disambiguation | batch_69e32b9aa8748190b248890aca86753d |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:31 a.m.