Triple
T20605608
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port Lincoln City Council |
E506300
|
entity |
| Predicate | coastalCouncil |
P73457
|
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: [Port Lincoln City Council, coastalCouncil, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coastalCouncil Context triple: [Port Lincoln City Council, coastalCouncil, true]
-
A.
isCoastalAuthority
chosen
Indicates that an entity has official jurisdiction or regulatory authority over a coastal area or coastline.
-
B.
isCoastalCommunity
Indicates that a community is located along a coast or shoreline and is directly associated with a nearby sea or ocean.
-
C.
isCoastalConstituency
Indicates that a political constituency is located on or directly adjacent to a sea or ocean coastline.
-
D.
hasCoastManagement
Indicates that an entity is responsible for or involved in the management, regulation, or oversight of coastal areas or coastal resources in relation to another entity or region.
-
E.
coastalInteraction
Indicates an interaction or relationship occurring between entities and a coastal environment, such as along shorelines or near the sea.
- 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_69e0b4bb2b4081908fa4a72444120f35 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6aa2452888190858d273430cd783d |
completed | April 20, 2026, 10:35 p.m. |
| PD | Predicate disambiguation | batch_69e5a00c43308190b7ea58d559257e07 |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:41 a.m.