Triple
T35337467
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Municipal government of Manta |
E1020502
|
entity |
| Predicate | operatesOnCoast |
P84004
|
FINISHED |
| Object | Pacific coast of Ecuador |
—
|
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 Ecuador | Statement: [Municipal government of Manta, operatesOnCoast, Pacific coast of Ecuador]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatesOnCoast Context triple: [Municipal government of Manta, operatesOnCoast, Pacific coast of Ecuador]
-
A.
isCoastalOn
Indicates that one entity is located along or directly borders the coastline of another entity (such as a body of water or sea).
-
B.
includesCoastOf
Indicates that one geographic or administrative entity encompasses or contains the coastline of another entity.
-
C.
basedOnCoast
Indicates that something is situated along, adjacent to, or directly influenced by a coastline.
-
D.
locatedOnCoastAt
chosen
Indicates that one entity is situated on the coastline at the specific location represented by 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_69f76debb4e08190be52d89b8af2392d |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a0136e4af808190b529d324bbf0c5d9 |
completed | May 11, 2026, 1:54 a.m. |
| PD | Predicate disambiguation | batch_6a01369141c4819091cb8064913a44ca |
completed | May 11, 2026, 1:53 a.m. |
Created at: May 3, 2026, 4:03 p.m.