Triple
T1121095
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lunan Bay |
E24611
|
entity |
| Predicate | hasCoastalProcess |
P18790
|
FINISHED |
| Object | tidal beach |
—
|
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: tidal beach | Statement: [Lunan Bay, hasCoastalProcess, tidal beach]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoastalProcess Context triple: [Lunan Bay, hasCoastalProcess, tidal beach]
-
A.
containsCoastalFeature
Indicates that one entity geographically includes or encompasses a coastal feature (such as a beach, cliff, bay, or shoreline) within its area or boundaries.
-
B.
isCoastalCommunity
Indicates that a community is located along a coast or shoreline and is directly associated with a nearby sea or ocean.
-
C.
hasCoastalRegion
Indicates that a place possesses at least one region that borders or is directly adjacent to a sea or ocean.
-
D.
geomorphologicalProcess
chosen
Indicates a relationship where one entity undergoes or is shaped by natural earth-surface processes that modify landforms and terrain structure.
-
E.
flowsAlongCoastOf
Indicates that something, typically a body of water or current, moves in a path that follows and runs adjacent to a coastline.
- 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_69a4940712c88190aa244f3fc6070a65 |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bc4bc21881909dcfe628f59f3e8c |
completed | March 1, 2026, 10:23 p.m. |
| PD | Predicate disambiguation | batch_69a4bb4562f48190831e959f5f309956 |
completed | March 1, 2026, 10:18 p.m. |
Created at: March 1, 2026, 7:43 p.m.