Triple
T33845953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Division of Kingsford Smith |
E867478
|
entity |
| Predicate | includesCoastalArea |
P5879
|
FINISHED |
| Object | Botany Bay |
E219329
|
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: Botany Bay | Statement: [Division of Kingsford Smith, includesCoastalArea, Botany Bay]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesCoastalArea Context triple: [Division of Kingsford Smith, includesCoastalArea, Botany Bay]
-
A.
includesCoastOf
Indicates that one geographic or administrative entity encompasses or contains the coastline of another entity.
-
B.
isCoastalArea
Indicates that a given area is located along or directly adjacent to a sea or ocean coastline.
-
C.
isCoastalResidentialAreaOf
Indicates that a residential area is located along or near the coast of a specified geographic or administrative region.
-
D.
includesCoastalTown
Indicates that a geographic area or region contains at least one town located on or directly adjacent to a coastline.
-
E.
containsCoastalFeature
chosen
Indicates that one entity geographically includes or encompasses a coastal feature (such as a beach, cliff, bay, or shoreline) within its area or boundaries.
- 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_69f349937b648190a34ada70f6a2b534 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a036c1282748190a820562bcd9aa5d9 |
completed | May 12, 2026, 6:06 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a366eb1b49881908d3c0c5904d30fd3 |
completed | June 20, 2026, 10:42 a.m. |
| PD | Predicate disambiguation | batch_6a036bb5ca0c8190bd50abc197960b41 |
completed | May 12, 2026, 6:04 p.m. |
Created at: May 1, 2026, 1:47 a.m.