Triple
T24058542
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Porth Neigwl |
E595876
|
entity |
| Predicate | hasBackshore |
P6651
|
FINISHED |
| Object | dunes and low cliffs |
—
|
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: dunes and low cliffs | Statement: [Porth Neigwl, hasBackshore, dunes and low cliffs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBackshore Context triple: [Porth Neigwl, hasBackshore, dunes and low cliffs]
-
A.
hasShoreOn
Indicates that one geographic entity borders or is directly adjacent to the shore of another body of water.
-
B.
shoreHas
Indicates that a shore possesses, contains, or is characterized by a particular feature, object, or attribute.
-
C.
hasShoreFeature
chosen
Indicates that a shore or coastline possesses a specific physical or environmental feature.
-
D.
hasLongShoreline
Indicates that an entity possesses an extensive or unusually long shoreline relative to typical cases.
-
E.
shoreType
Indicates the kind or classification of a shoreline associated with a body of water or coastal area.
- 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_69e288c184b081909f1f1751fb8e299a |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1da52b9d48190b503fad5ff70e4c6 |
completed | April 29, 2026, 10:15 a.m. |
| PD | Predicate disambiguation | batch_69f1764b1d4c8190b12590c6339c31c1 |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 10:36 p.m.