Triple
T35159952
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Cape Bay |
E1015237
|
entity |
| Predicate | hasApproxDistanceFromCockleCreek |
P195420
|
FINISHED |
| Object | about 7 to 9 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 7 to 9 kilometres one way | Statement: [South Cape Bay, hasApproxDistanceFromCockleCreek, about 7 to 9 kilometres one way]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApproxDistanceFromCockleCreek Context triple: [South Cape Bay, hasApproxDistanceFromCockleCreek, about 7 to 9 kilometres one way]
-
A.
hasApproximateRoundTripDistanceFromMaroonLake
Indicates that an entity has an approximate total round-trip distance measured from Maroon Lake.
-
B.
hasNearbyCove
Indicates that one location is situated close to a small sheltered bay or cove.
-
C.
hasNearbyCoast
Indicates that one location is situated close to a coastline or seashore.
-
D.
hasLowerCourseNear
Indicates that the lower section of a course (such as a river or path) is located in close proximity to a specified reference entity or area.
-
E.
distanceFromGillam_km
Indicates the distance, measured in kilometers, between an entity and the location Gillam.
- 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_69f76ddb3a708190b521ba2970b17178 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fdd07a34c08190982b8c61c2775cf6 |
completed | May 8, 2026, noon |
| PD | Predicate disambiguation | batch_69fdbd25c7908190b72fca8de7ce503f |
completed | May 8, 2026, 10:38 a.m. |
| PDg | Predicate description generation | batch_69fdd07724f88190a33ec602642d2ea3 |
completed | May 8, 2026, noon |
Created at: May 3, 2026, 4:02 p.m.