Triple
T14682413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toowoomba Regional Council area |
E344820
|
entity |
| Predicate | hasTown |
P847
|
FINISHED |
| Object | Oakey |
E376392
|
NE 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: Oakey | Statement: [Toowoomba Regional Council area, hasTown, Oakey]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Oakey Context triple: [Toowoomba Regional Council area, hasTown, Oakey]
-
A.
Oakey
chosen
Oakey is a rural town in Queensland, Australia, situated on the Darling Downs west of Toowoomba.
-
B.
Oakes
Oakes is a surname of English origin borne by various notable individuals, including Patricia Luisa Oakes.
-
C.
Walganus
Walganus is an alternative name or variant form of the name Walwen, likely referring to the same historical or legendary figure.
-
D.
Tallassee
Tallassee is a small city in central Alabama known for its location along the Tallapoosa River and its historic textile mill heritage.
-
E.
Mauldin
Mauldin is a city in South Carolina, United States, known as a suburban community within the Greenville metropolitan area.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d822e34b348190ada4d1cdb6c7c226 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb56a51ec8190941684fd562a7182 |
completed | April 14, 2026, 9:45 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fde182dab08190aac2ff2db666ee69 |
completed | May 8, 2026, 1:13 p.m. |
Created at: April 10, 2026, 1:28 a.m.