Triple
T25351585
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Albury–Wodonga cross-border region |
E635700
|
entity |
| Predicate | hasCityInVictoria |
P160858
|
FINISHED |
| Object | Wodonga |
—
|
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: Wodonga | Statement: [Albury–Wodonga cross-border region, hasCityInVictoria, Wodonga]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCityInVictoria Context triple: [Albury–Wodonga cross-border region, hasCityInVictoria, Wodonga]
-
A.
hasInlandCity
Indicates that one entity has, contains, or is associated with a city located inland (away from the coast or major bodies of water).
-
B.
containsCapitalCity
Indicates that a geographic or political region includes within its boundaries the capital city associated with it.
-
C.
capitalCityOfStateLocatedIn
Indicates that a city serves as the capital of a state, and that state is located within a specified larger geographic or political region.
-
D.
isEasternSuburbOf
Indicates that one place is a suburb located to the east of another place.
-
E.
isPartOfCapitalCityOf
Indicates that something is a constituent or component of the capital city belonging to a particular political or administrative entity.
- 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_69e75a9ac5d881909387ed766e20cd47 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f60ac643108190ae81561267155791 |
completed | May 2, 2026, 2:31 p.m. |
| PD | Predicate disambiguation | batch_69f602ce79ec8190b8336c2b9de18ac7 |
completed | May 2, 2026, 1:57 p.m. |
| PDg | Predicate description generation | batch_69f606c15af88190958856a9e467b826 |
completed | May 2, 2026, 2:14 p.m. |
Created at: April 21, 2026, 1:34 p.m.