Triple
T6892622
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wiradjeri |
E159082
|
entity |
| Predicate | hasPlaceNamesIn |
P73979
|
FINISHED |
| Object | central New South Wales |
—
|
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: central New South Wales | Statement: [Wiradjeri, hasPlaceNamesIn, central New South Wales]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlaceNamesIn Context triple: [Wiradjeri, hasPlaceNamesIn, central New South Wales]
-
A.
hasPlaceNamedAfter
Indicates that one place is named in honor of or derived from the name of another place.
-
B.
toponymContains
Indicates that one geographic place name spatially includes or encompasses another place name within its boundaries.
-
C.
hasNotableToponym
Indicates that an entity is associated with a place name that is particularly notable, distinctive, or significant.
-
D.
isPopulatedPlaceIn
Indicates that a populated place (such as a city, town, or village) is located within a specified larger geographic or administrative area.
-
E.
isPopulatedPlace
Indicates that the subject is a geographic location where people live or have lived, such as a city, town, village, or settlement.
- 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_69c6883568c8819081db6407e892cccc |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d930ab548190953291d63cbc721b |
completed | March 27, 2026, 7:23 p.m. |
| PD | Predicate disambiguation | batch_69c6d7b53e9881909ec298daa9f1913b |
completed | March 27, 2026, 7:17 p.m. |
| PDg | Predicate description generation | batch_69c6d8c48ba48190b8d3aa7b8d22816b |
completed | March 27, 2026, 7:21 p.m. |
Created at: March 27, 2026, 2:24 p.m.