Triple
T25351584
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Albury–Wodonga cross-border region |
E635700
|
entity |
| Predicate | hasCityInNewSouthWales |
P115312
|
FINISHED |
| Object | Albury |
—
|
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: Albury | Statement: [Albury–Wodonga cross-border region, hasCityInNewSouthWales, Albury]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCityInNewSouthWales Context triple: [Albury–Wodonga cross-border region, hasCityInNewSouthWales, Albury]
-
A.
associatedCityNSW
chosen
Indicates that an entity is associated with a specific city located in New South Wales (NSW), Australia.
-
B.
populationRankInNSW
Indicates the relative position of an entity in terms of population size compared to other entities within New South Wales (NSW).
-
C.
isEasternSuburbOf
Indicates that one place is a suburb located to the east of another place.
-
D.
keyAustralianCityForRelations
Indicates that a city is a primary or strategically important Australian location for managing or conducting relations (such as diplomatic, economic, or organizational relationships).
-
E.
teamFromNewSouthWales
Indicates that a team is based in, originates from, or represents the region of New South Wales.
- 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_69e75a9ac5d881909387ed766e20cd47 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f5ffc74fa481909b4fe24a9337f9eb |
completed | May 2, 2026, 1:44 p.m. |
| PD | Predicate disambiguation | batch_69f5f7f99dc08190afcfb3bc4dfbec1d |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 21, 2026, 1:34 p.m.