Triple
T12185821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Foxton |
E290330
|
entity |
| Predicate | hasRiverMouthNearby |
P28855
|
FINISHED |
| Object | Manawatū River mouth |
—
|
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: Manawatū River mouth | Statement: [Foxton, hasRiverMouthNearby, Manawatū River mouth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRiverMouthNearby Context triple: [Foxton, hasRiverMouthNearby, Manawatū River mouth]
-
A.
riverMouthRegion
Indicates the region or area where a river flows into a larger body of water, such as a sea, lake, or another river.
-
B.
hasHumanSettlementAtMouth
Indicates that a human settlement is located at the mouth (outflow point) of a geographic feature such as a river or valley.
-
C.
riverMouthBasin
Indicates that a river’s mouth lies within or drains into a particular drainage basin.
-
D.
hasEstuaryNear
chosen
Indicates that the estuary of a water body is located in close proximity to a specified place or feature.
-
E.
riverMouthCountry
Indicates the country in which a river’s mouth (where it flows into another body of water) is located.
- 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_69d6ab64de5881908d56eb7a75c6cc69 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d91a83012c81908d04bbab5fdcd8c2 |
completed | April 10, 2026, 3:42 p.m. |
| PD | Predicate disambiguation | batch_69d91510a258819090ef8fbdc2d8707b |
completed | April 10, 2026, 3:19 p.m. |
Created at: April 8, 2026, 9:50 p.m.