Triple
T14155127
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beresfield |
E350795
|
entity |
| Predicate | distanceFromNewcastleCBD_km |
P113033
|
FINISHED |
| Object | 22 |
—
|
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: 22 | Statement: [Beresfield, distanceFromNewcastleCBD_km, 22]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromNewcastleCBD_km Context triple: [Beresfield, distanceFromNewcastleCBD_km, 22]
-
A.
distanceFromNewcastle
Indicates the spatial distance between a given entity or location and the city of Newcastle.
-
B.
distanceToNewcastle_km
Indicates the physical distance, measured in kilometers, between a given location and Newcastle.
-
C.
distanceFromGosford_km
Indicates the physical distance, measured in kilometers, between an entity’s location and Gosford.
-
D.
distanceFromMurwillumbah
Indicates the spatial distance separating an entity from the location of Murwillumbah.
-
E.
distanceFromSydney
Indicates the spatial distance between a given location and the city of Sydney.
- 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_69d8278775fc8190b0802d22ca2f495d |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de6135744c81909a43d659f5fe2895 |
completed | April 14, 2026, 3:45 p.m. |
| PD | Predicate disambiguation | batch_69de05b8434c81908c33b1b513463b12 |
completed | April 14, 2026, 9:15 a.m. |
| PDg | Predicate description generation | batch_69de239a02e881909b0e2679487e4ab2 |
completed | April 14, 2026, 11:23 a.m. |
Created at: April 10, 2026, 12:58 a.m.