Triple
T38189726
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guichen Bay |
E1005419
|
entity |
| Predicate | hasCoastalTownOnShore |
P969
|
FINISHED |
| Object | Robe, South Australia |
E1001944
|
NE 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: Robe, South Australia | Statement: [Guichen Bay, hasCoastalTownOnShore, Robe, South Australia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoastalTownOnShore Context triple: [Guichen Bay, hasCoastalTownOnShore, Robe, South Australia]
-
A.
hasCityOnShore
chosen
Indicates that a city is located on or directly adjacent to the shore of a body of water.
-
B.
hasCoastline
Indicates that a geographic entity is bordered by and directly touches a sea or ocean along part of its boundary.
-
C.
hasOnItsCoast
Indicates that a geographic entity (such as a country or region) borders and includes along its shoreline another entity (such as a sea, ocean, or body of water).
-
D.
isCoastalSettlementOf
Indicates that a settlement is located on or near the coast within the territory of a specified geographic or administrative area.
-
E.
hasCapitalCityOnCoast
Indicates that the capital city of an entity is geographically located on a coastline.
- F. None of above.
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_69f76dbd22f48190940318cea061e8bb |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037df1223c8190a5d61e4f8e6fd613 |
completed | May 12, 2026, 7:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a4193bb36048190acab9eff87ca32c4 |
completed | June 28, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_6a037a1ad6c48190bfe35d350c1b4751 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:29 p.m.