Triple
T26240669
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mildura–Sydney |
E656302
|
entity |
| Predicate | connectsRegionalCity |
P180202
|
FINISHED |
| Object | Mildura |
—
|
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: Mildura | Statement: [Mildura–Sydney, connectsRegionalCity, Mildura]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectsRegionalCity Context triple: [Mildura–Sydney, connectsRegionalCity, Mildura]
-
A.
connectsProvinceOrRegion
Indicates that one entity serves to link or provide a connection between a specific province or region and another entity.
-
B.
linkedCityRegion
Indicates that a city is associated with, belongs to, or is administratively connected to a specific region.
-
C.
connectsCity
Indicates a relationship where one entity serves as a link or route that joins or provides direct access between two cities.
-
D.
terminalCityRegion
Indicates that a city serves as the terminal (end-point) location within a specified region for a route, line, or connection.
-
E.
connectsCityTo
Indicates a relationship in which a route, infrastructure, or link joins one city to another, enabling connection or interaction between them.
- 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_69ee5b4c59a881909d9ee4fd013fffd5 |
completed | April 26, 2026, 6:37 p.m. |
| NER | Named-entity recognition | batch_69f739a638748190808e7a2930dce16e |
completed | May 3, 2026, 12:03 p.m. |
| PD | Predicate disambiguation | batch_69f732f2dc6c8190a4e86da98cc5eb05 |
completed | May 3, 2026, 11:35 a.m. |
| PDg | Predicate description generation | batch_69f739a58b3c81908abc2b8738a65678 |
completed | May 3, 2026, 12:03 p.m. |
Created at: April 26, 2026, 9:03 p.m.