Triple
T22298269
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Goodyear |
E551180
|
entity |
| Predicate | adjacentTo |
P224
|
FINISHED |
| Object | Avondale |
—
|
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: Avondale | Statement: [Goodyear, adjacentTo, Avondale]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Avondale Context triple: [Goodyear, adjacentTo, Avondale]
-
A.
Avondale
chosen
Avondale is a suburban city in the Phoenix metropolitan area of Arizona, known for its rapid growth and proximity to major regional amenities.
-
B.
Avondale
Avondale is a residential neighborhood on Chicago’s Northwest Side known for its diverse communities, historic Polish and Latino roots, and easy access to public transit.
-
C.
Avondale
Avondale is a residential suburb of Auckland, New Zealand, known for its diverse community and proximity to the city center.
-
D.
Avondale
Avondale is a well-known residential and commercial suburb of Harare, Zimbabwe, noted for its shopping centers and relatively affluent character.
-
E.
Avondale
Avondale is a place in Scotland whose name was used in the noble title "Duke of Clarence and Avondale" in the British peerage.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e11e45fb848190a1b2ae21296e3a5f |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f1572200c88190b9413286136fef15 |
completed | April 29, 2026, 12:56 a.m. |
Created at: April 16, 2026, 8:41 p.m.