Triple
T9072439
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Loreto |
E217400
|
entity |
| Predicate | coastalStatus |
P21854
|
FINISHED |
| Object | coastal town |
—
|
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: coastal town | Statement: [Loreto, coastalStatus, coastal town]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coastalStatus Context triple: [Loreto, coastalStatus, coastal town]
-
A.
isCoastalOn
Indicates that one entity is located along or directly borders the coastline of another entity (such as a body of water or sea).
-
B.
hasCoastalCharacteristic
Indicates that an entity possesses a feature, quality, or condition specifically related to coastal or shoreline environments.
-
C.
isCoastalCommunity
chosen
Indicates that a community is located along a coast or shoreline and is directly associated with a nearby sea or ocean.
-
D.
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.
-
E.
hasHeritageCoastStatus
Indicates that a coastal area has been officially designated as a Heritage Coast, recognizing its special natural, scenic, or environmental value.
- 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_69ca83d6c14c8190bc056d927f00a2a2 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc955ffa04819086be5763133c5067 |
completed | April 1, 2026, 3:47 a.m. |
| PD | Predicate disambiguation | batch_69cc65f881248190bfd220bb28a9fb5f |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:12 p.m.