Triple
T14006045
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Daleys Point |
E336948
|
entity |
| Predicate | isWaterfrontSuburb |
P112119
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Daleys Point, isWaterfrontSuburb, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isWaterfrontSuburb Context triple: [Daleys Point, isWaterfrontSuburb, true]
-
A.
isWaterfrontThoroughfare
Indicates that a thoroughfare (such as a road, street, or path) is located directly along or adjacent to a body of water.
-
B.
isWaterfrontBuilding
Indicates that a building is located directly adjacent to a body of water, such as a river, lake, or ocean.
-
C.
hasWaterfrontType
Indicates that an entity is associated with a specific type or category of waterfront (e.g., oceanfront, lakefront, riverfront).
-
D.
isCoastalCitySuburb
Indicates that a suburb is located within or adjacent to a city that lies on a coastline, functioning as a suburban area of that coastal city.
-
E.
hasWaterfrontArea
Indicates that an entity possesses or includes an area directly adjacent to or bordering a body of water.
- 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_69d81c645c5c8190b1fd16a285a1b78a |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2ed327d88190a53af5768468a8eb |
completed | April 14, 2026, 12:10 p.m. |
| PD | Predicate disambiguation | batch_69dd465dfbc4819090d8c61fd572d35f |
completed | April 13, 2026, 7:39 p.m. |
| PDg | Predicate description generation | batch_69de01ed2098819088ec45069f6f2609 |
completed | April 14, 2026, 8:59 a.m. |
Created at: April 9, 2026, 10:19 p.m.