Triple
T31488388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Bull sandbank |
E803339
|
entity |
| Predicate | coastTypeInfluenced |
P136457
|
FINISHED |
| Object | estuarine coast |
—
|
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: estuarine coast | Statement: [North Bull sandbank, coastTypeInfluenced, estuarine coast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coastTypeInfluenced Context triple: [North Bull sandbank, coastTypeInfluenced, estuarine coast]
-
A.
coastType
Indicates the specific kind or classification of a coastline associated with a geographic area.
-
B.
hasCoastlineInfluence
chosen
Indicates that one entity exerts an effect or is significantly shaped by the presence, characteristics, or proximity of a coastline associated with another entity.
-
C.
coastalInteraction
Indicates an interaction or relationship occurring between entities and a coastal environment, such as along shorelines or near the sea.
-
D.
oceanInfluence
Indicates how the presence, properties, or behavior of an ocean affects another entity, condition, or process.
-
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_69f348ca04508190ba9379b5329dfd75 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6afebd7ec8190ab696f363d84abf0 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca3dedc81908b519d53d2909868 |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 30, 2026, 9:36 p.m.