Triple
T14580005
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Freshwater Bay |
E342165
|
entity |
| Predicate | hasNaturalBoundary |
P6131
|
FINISHED |
| Object | coastline |
—
|
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: coastline | Statement: [Freshwater Bay, hasNaturalBoundary, coastline]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNaturalBoundary Context triple: [Freshwater Bay, hasNaturalBoundary, coastline]
-
A.
hasBoundaryFeature
chosen
Indicates that a boundary (such as an edge, border, or limit) of one entity is characterized, marked, or defined by a specific feature or element.
-
B.
isBoundaryFor
Indicates that one entity serves as the limiting edge, border, or enclosing extent that defines the spatial or conceptual bounds of another entity.
-
C.
hasBoundaryShape
Indicates that an entity is associated with, or characterized by, a specific geometric or spatial shape of its boundary.
-
D.
hasBoundaryCriterion
Indicates that something is associated with a specific rule or condition used to define or limit its boundary.
-
E.
hasBoundaryUnit
Indicates that one entity uses or is associated with a specific unit of measurement for its boundary or limit.
- 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_69d822ddc0f081909cd8163c7de298cd |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb3f6f78c81908a30ecb4c025299d |
completed | April 14, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69de656a953481909a4645b004c40de7 |
completed | April 14, 2026, 4:03 p.m. |
Created at: April 10, 2026, 1:24 a.m.