Triple
T4448633
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metford |
E96350
|
entity |
| Predicate | distanceToMaitlandCBD |
P56574
|
FINISHED |
| Object | approximately 6 km east |
—
|
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: approximately 6 km east | Statement: [Metford, distanceToMaitlandCBD, approximately 6 km east]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToMaitlandCBD Context triple: [Metford, distanceToMaitlandCBD, approximately 6 km east]
-
A.
distanceToMildura_km
Indicates the physical distance, measured in kilometers, between a given location and Mildura.
-
B.
distanceFromGeorgeTown
Indicates the measured spatial distance between a given location and George Town.
-
C.
distanceToMelbourne
Indicates the spatial distance between a given location or entity and the city of Melbourne.
-
D.
distanceToMaroochydore
Indicates the measured distance from a given entity or location to Maroochydore.
-
E.
distanceFromGeelong
Indicates the spatial distance between a given entity or location and Geelong.
- F. None of above. chosen
Provenance (4 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_69b345415ba481908df738e7174448ba |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b355d45b748190b09b7067fc6279b0 |
completed | March 13, 2026, 12:09 a.m. |
| PD | Predicate disambiguation | batch_69b34f62c180819097ced38da2052207 |
completed | March 12, 2026, 11:42 p.m. |
| PDg | Predicate description generation | batch_69b35034cd248190bae09e9d090e13ec |
completed | March 12, 2026, 11:45 p.m. |
Created at: March 12, 2026, 11:32 p.m.