Triple
T15806000
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gorokan |
E383217
|
entity |
| Predicate | distanceToNewcastleCBD_km |
P111976
|
FINISHED |
| Object | approximately 55 |
—
|
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 55 | Statement: [Gorokan, distanceToNewcastleCBD_km, approximately 55]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToNewcastleCBD_km Context triple: [Gorokan, distanceToNewcastleCBD_km, approximately 55]
-
A.
distanceFromNewcastleCBD_km
Indicates the physical distance, measured in kilometers, between an entity and the central business district (CBD) of Newcastle.
-
B.
distanceToNewcastle_km
chosen
Indicates the physical distance, measured in kilometers, between a given location and Newcastle.
-
C.
distanceFromNewcastle
Indicates the spatial distance between a given entity or location and the city of Newcastle.
-
D.
distanceFromGosford_km
Indicates the physical distance, measured in kilometers, between an entity’s location and Gosford.
-
E.
distanceFromMurwillumbah
Indicates the spatial distance separating an entity from the location of Murwillumbah.
- 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_69d86da2858c819090cc8481e7207b6e |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0b52682548190998d8b6a08982877 |
completed | April 16, 2026, 10:08 a.m. |
| PD | Predicate disambiguation | batch_69e0053b847c8190945726c3ddac21cc |
completed | April 15, 2026, 9:38 p.m. |
Created at: April 10, 2026, 4:48 a.m.