Triple
T25340962
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adelaide 500 |
E635410
|
entity |
| Predicate | cityStreetUse |
P121309
|
FINISHED |
| Object | Victoria Park area |
—
|
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: Victoria Park area | Statement: [Adelaide 500, cityStreetUse, Victoria Park area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cityStreetUse Context triple: [Adelaide 500, cityStreetUse, Victoria Park area]
-
A.
cityStreetUsed
chosen
Indicates that a particular city street is utilized or traversed in the course of some activity, route, or event.
-
B.
roadUse
Indicates that an entity utilizes or travels on a particular road or roadway for movement or transport.
-
C.
hasBuildingUseAlongStreet
Indicates that a building located along a particular street is used for a specified purpose or function in relation to that street.
-
D.
isUrbanStreet
Indicates that a given street is located within an urban area or city environment rather than a rural or suburban setting.
-
E.
betweenStreets
Indicates that one location is situated between two specified streets, typically along a road segment bounded by those streets.
- 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_69e75a99bd6481909476115b35b9a8e4 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f498b6672881909d3257dc6b52caa3 |
completed | May 1, 2026, 12:12 p.m. |
| PD | Predicate disambiguation | batch_69f45d0dbc8c8190beecce679fce90a4 |
completed | May 1, 2026, 7:58 a.m. |
Created at: April 21, 2026, 1:32 p.m.