Triple
T36742543
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Buller River |
E907660
|
entity |
| Predicate | hasTownAtMouth |
P93322
|
FINISHED |
| Object | Westport |
—
|
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: Westport | Statement: [Buller River, hasTownAtMouth, Westport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTownAtMouth Context triple: [Buller River, hasTownAtMouth, Westport]
-
A.
hasHumanSettlementAtMouth
chosen
Indicates that a human settlement is located at the mouth (outflow point) of a geographic feature such as a river or valley.
-
B.
cityAtMouth
Indicates that a city is located at or very near the mouth (outlet) of a river.
-
C.
hasIslandAtMouth
Indicates that a geographic feature, typically a river, has an island located at or near its mouth where it meets a larger body of water.
-
D.
hasTownOnRiver
Indicates that a town is situated on or directly adjacent to a particular river.
-
E.
hasMouthOnCoastOf
Indicates that one entity’s mouth or outlet is located on the coast of another entity.
- 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_69f76e76d10881909ec1679bc043108c |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fd6dbd1b648190b1a0b391c03aebc5 |
completed | May 8, 2026, 4:59 a.m. |
| PD | Predicate disambiguation | batch_69fd6a9020548190bbfa845360ac85fb |
completed | May 8, 2026, 4:46 a.m. |
Created at: May 3, 2026, 4:12 p.m.