Triple
T1298851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dalgety Bay |
E27715
|
entity |
| Predicate | locatedOnShore |
P1489
|
FINISHED |
| Object | northern shore of the Firth of Forth |
—
|
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: northern shore of the Firth of Forth | Statement: [Dalgety Bay, locatedOnShore, northern shore of the Firth of Forth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedOnShore Context triple: [Dalgety Bay, locatedOnShore, northern shore of the Firth of Forth]
-
A.
hasCityOnShore
Indicates that a city is located on or directly adjacent to the shore of a body of water.
-
B.
hasShoreOn
Indicates that one geographic entity borders or is directly adjacent to the shore of another body of water.
-
C.
basedOnCoast
Indicates that something is situated along, adjacent to, or directly influenced by a coastline.
-
D.
locatedOnWaterbody
chosen
Indicates that an entity is situated on or directly adjacent to a specified body of water.
-
E.
locatedInBodyOfWater
Indicates that an entity is situated within or on the surface of a specific body of water.
- 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_69a496d6682881909ba658f1c1e0e2b0 |
completed | March 1, 2026, 7:43 p.m. |
| NER | Named-entity recognition | batch_69a4c3bb3a9c81909db2ad91defd87b6 |
completed | March 1, 2026, 10:54 p.m. |
| PD | Predicate disambiguation | batch_69a4bee64d908190b6a9bb479959d523 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:51 p.m.