Triple
T14225396
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maitland Bay |
E352603
|
entity |
| Predicate | approximateWalkDistanceToBeach |
P37106
|
FINISHED |
| Object | about 1.5 kilometres one way |
—
|
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: about 1.5 kilometres one way | Statement: [Maitland Bay, approximateWalkDistanceToBeach, about 1.5 kilometres one way]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateWalkDistanceToBeach Context triple: [Maitland Bay, approximateWalkDistanceToBeach, about 1.5 kilometres one way]
-
A.
nearestMajorBeach
Indicates the relationship where a location is associated with the closest significant or well-known beach to it.
-
B.
proximityToLandmark
Indicates a spatial relationship where one entity is located near or close to a specified landmark.
-
C.
hasBeachNearby
Indicates that one location is situated close enough to another location to have convenient access to a beach.
-
D.
distanceFromCoast
Indicates the measured spatial separation between a location and the nearest point on a coastline.
-
E.
approximateDistanceFrom
chosen
Indicates an estimated or rough measure of how far one entity is from another.
- 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_69d8278a06e481908b5d6af0a8afe737 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de6228e53c8190abbe4e2d88a7362a |
completed | April 14, 2026, 3:50 p.m. |
| PD | Predicate disambiguation | batch_69de05bf069c8190b69f00f00f5eb126 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 1:06 a.m.