Triple
T11192167
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paraburdoo |
E264827
|
entity |
| Predicate | distanceFromMajorRegion |
P76218
|
FINISHED |
| Object | remote from major urban centres |
—
|
LITERAL FINISHED |
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: remote from major urban centres | Statement: [Paraburdoo, distanceFromMajorRegion, remote from major urban centres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromMajorRegion Context triple: [Paraburdoo, distanceFromMajorRegion, remote from major urban centres]
-
A.
distanceFromMajorCity
Indicates the measured distance between a given location and a specified major city.
-
B.
distanceFromCoreRegion
chosen
Indicates the spatial or conceptual distance between an entity and a defined core or central region.
-
C.
distanceFromDowntown
Indicates the physical distance between a given location and the central downtown area.
-
D.
districtHeadquartersDistance
Indicates the distance between a place and its corresponding district headquarters.
-
E.
shareMajorCityRegion
Indicates that two entities are associated with the same major city or its surrounding metropolitan region.
- 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_69d6aa9eb9248190b20211772621b4bc |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8be025481909d311b587418dfb2 |
completed | April 9, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69d75cf4461c8190af84060f7db83211 |
completed | April 9, 2026, 8:01 a.m. |
Created at: April 8, 2026, 9:29 p.m.