Triple
T27052460
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barham |
E684808
|
entity |
| Predicate | nearestMajorRiverTown |
P166639
|
FINISHED |
| Object | Echuca |
—
|
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: Echuca | Statement: [Barham, nearestMajorRiverTown, Echuca]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearestMajorRiverTown Context triple: [Barham, nearestMajorRiverTown, Echuca]
-
A.
hasMajorTownOnRiver
Indicates that a major town is located on and directly associated with a particular river.
-
B.
hasMajorCityOnRiver
Indicates that a major city is located on and directly associated with a particular river.
-
C.
hasTownOnRiver
Indicates that a town is situated on or directly adjacent to a particular river.
-
D.
largestCityLocatedOnRiver
Indicates that a city is the largest (by population or size) among all cities situated on a given river.
-
E.
capitalCityOnRiver
Indicates that a capital city is located on and directly adjacent to a particular river.
- F. None of above. chosen
Provenance (4 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_69ef14829fac8190914bef9ecc3005d7 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f662a29b3881909957a7e3b986653c |
completed | May 2, 2026, 8:46 p.m. |
| PD | Predicate disambiguation | batch_69f660eea4648190b0d5e24293607813 |
completed | May 2, 2026, 8:39 p.m. |
| PDg | Predicate description generation | batch_69f661b47d088190934f63884a203261 |
completed | May 2, 2026, 8:42 p.m. |
Created at: April 27, 2026, 8:15 a.m.