Triple
T32305032
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bayside area of Melbourne |
E825339
|
entity |
| Predicate | locatedInDirectionFromMelbourneCBD |
P27558
|
FINISHED |
| Object | southeast |
—
|
LITERAL 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: southeast | Statement: [Bayside area of Melbourne, locatedInDirectionFromMelbourneCBD, southeast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInDirectionFromMelbourneCBD Context triple: [Bayside area of Melbourne, locatedInDirectionFromMelbourneCBD, southeast]
-
A.
directionFromMelbourne
chosen
Indicates the compass direction in which one entity is located relative to Melbourne.
-
B.
directionToMelbourne
Indicates the directional relationship pointing from a given location toward Melbourne.
-
C.
directionFromCanberraCBD
Indicates the compass direction in which one location lies relative to the Canberra Central Business District (CBD).
-
D.
directionFromFlindersStreet
Indicates the compass direction or bearing of an entity when measured from Flinders Street as the point of reference.
-
E.
directionFromBrisbaneCBD
Indicates the compass direction or relative bearing of a place or object when measured outward from the Brisbane Central Business District.
- 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_69f349115304819084ee91d345b6c8aa |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a0235be932081908857bc3a77c27e7d |
completed | May 11, 2026, 8:02 p.m. |
| PD | Predicate disambiguation | batch_6a022c865dec81909e02b2f330e987e6 |
completed | May 11, 2026, 7:22 p.m. |
Created at: May 1, 2026, 12:45 a.m.