Triple
T15498739
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cooroy |
E378891
|
entity |
| Predicate | nearbyLocality |
P4647
|
FINISHED |
| Object | Pomona |
E357542
|
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: Pomona | Statement: [Cooroy, nearbyLocality, Pomona]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pomona Context triple: [Cooroy, nearbyLocality, Pomona]
-
A.
Pomona
Pomona is a city in eastern Los Angeles County, California, known for hosting the LA County Fair and for its historic downtown and arts district.
-
B.
Pomona
chosen
Pomona is a rural town in Queensland, Australia, known for its heritage architecture and proximity to the Noosa hinterland.
-
C.
Pomona
Pomona is an ancient Maya archaeological site in the western lowlands of present-day Mexico, known for its sculpted monuments and inscriptions.
-
D.
Pomona
Pomona is a former name of the city now known as Manvel, located in Brazoria County, Texas.
-
E.
Pomona
Pomona is an unincorporated community and census-designated place located within Galloway Township in Atlantic County, New Jersey.
- 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_69d85cd53a7c819080f5b9042c4c199e |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e03fb0aee081909db1c54349ec8492 |
completed | April 16, 2026, 1:47 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff3667a53c81908be789f99e580265 |
completed | May 9, 2026, 1:28 p.m. |
Created at: April 10, 2026, 3:53 a.m.