Triple
T25451951
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Macquarie River region |
E637803
|
entity |
| Predicate | hasUpstreamCity |
P72891
|
FINISHED |
| Object | Bathurst |
—
|
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: Bathurst | Statement: [Macquarie River region, hasUpstreamCity, Bathurst]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUpstreamCity Context triple: [Macquarie River region, hasUpstreamCity, Bathurst]
-
A.
upstreamCity
chosen
Indicates that one city is located upstream along a river or waterway relative to another city.
-
B.
hasTargetCity
Indicates that something is directed toward, intended for, or specifically associated with a particular city as its target.
-
C.
hasCityPair
Indicates a relationship that links two cities considered as a connected or associated pair, often for purposes such as travel, trade, or comparison.
-
D.
hasIntermediateCity
Indicates that there is a city located between two other places along a route or connection.
-
E.
hasGatewayCity
Indicates that one place serves as the primary gateway city (main entry or transit hub) for accessing another place.
- 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_69e75db7c5048190b8da9cd7eeedb610 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f707c8408190b0405250a2c02a03 |
completed | May 2, 2026, 1:07 p.m. |
| PD | Predicate disambiguation | batch_69f4683b34748190818428489a226124 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 21, 2026, 2:03 p.m.