Triple
T25718803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mossy River |
E644929
|
entity |
| Predicate | hasMouthInProvince |
P32498
|
FINISHED |
| Object | Manitoba |
—
|
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: Manitoba | Statement: [Mossy River, hasMouthInProvince, Manitoba]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMouthInProvince Context triple: [Mossy River, hasMouthInProvince, Manitoba]
-
A.
isInProvince
Indicates that one entity (typically a place or city) is located within the administrative boundaries of a specified province.
-
B.
hasProvinceOrRegion
Indicates that one entity includes, is associated with, or is located within a specific province or region as an administrative or geographic subdivision.
-
C.
stationedInProvince
Indicates that an entity is assigned or based in a particular province as its location or area of operation.
-
D.
mouthLocatedInAdministrativeEntity
chosen
Indicates that the place where a river ends (its mouth) is situated within a specific administrative region or jurisdiction.
-
E.
hasMouthPositionRelativeToCity
Indicates the spatial position of a river’s mouth in relation to a specified city.
- 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_69e77e8476fc8190bd5e9d05b89fad0a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f674e06c9481909ed0ea736408f0d7 |
completed | May 2, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69f673c2f81c8190bf369226306eef09 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 21, 2026, 9:51 p.m.