Triple
T35765153
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yoogali, New South Wales, Australia |
E1033994
|
entity |
| Predicate | hasNearbyRegionalCity |
P84435
|
FINISHED |
| Object | Griffith, New South Wales |
—
|
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: Griffith, New South Wales | Statement: [Yoogali, New South Wales, Australia, hasNearbyRegionalCity, Griffith, New South Wales]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyRegionalCity Context triple: [Yoogali, New South Wales, Australia, hasNearbyRegionalCity, Griffith, New South Wales]
-
A.
hasNearbyCityArea
Indicates that one area is geographically close to or adjacent to a city area.
-
B.
hasNearbyCityFunction
Indicates that one entity serves as a nearby urban center or city-like service hub for another entity.
-
C.
hasNearbyMajorCityCountry
Indicates that an entity has a nearby major city located in the specified country.
-
D.
hasRegionalCenterNearby
chosen
Indicates that a regional center is located in close proximity to the referenced entity.
-
E.
hasNearbyUSCity
Indicates that one location has at least one city in the United States situated within a specified nearby distance.
- 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_69f76e13edd081909101629aa829c4ad |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a002e71bdc48190b922f2d3b362d259 |
completed | May 10, 2026, 7:06 a.m. |
| PD | Predicate disambiguation | batch_6a002e1a28708190b65f9e657c770bab |
completed | May 10, 2026, 7:04 a.m. |
Created at: May 3, 2026, 4:06 p.m.