Triple
T26164677
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ECHU |
E654214
|
entity |
| Predicate | stationLocatedIn |
P40
|
FINISHED |
| Object | Echuca, Victoria, Australia |
—
|
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, Victoria, Australia | Statement: [ECHU, stationLocatedIn, Echuca, Victoria, Australia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stationLocatedIn Context triple: [ECHU, stationLocatedIn, Echuca, Victoria, Australia]
-
A.
areLocatedAt
Indicates that one or more entities occupy or exist at a specific location or place.
-
B.
locatedIn
chosen
Indicates that one entity exists or is situated within the spatial, administrative, or conceptual boundaries of another entity.
-
C.
oftenLocatedAt
Indicates that an entity is frequently or commonly found at, or associated with being in, a particular location.
-
D.
cityLocatedIn
Indicates that a city is geographically situated within a specified larger administrative or territorial region.
-
E.
flagshipStationLocation
Indicates the location where an organization’s primary or flagship station is situated.
- 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_69ee5b44391c81908bdbd8813ba9aa99 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f612607c388190ab61d1ac7d18e08d |
completed | May 2, 2026, 3:04 p.m. |
| PD | Predicate disambiguation | batch_69f611a9272881909093360472be832c |
completed | May 2, 2026, 3 p.m. |
Created at: April 26, 2026, 8:32 p.m.