Triple
T24753005
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Firth of Forth basin |
E619198
|
entity |
| Predicate | hasMajorCityOnEstuary |
P33130
|
FINISHED |
| Object | Dunfermline |
—
|
NE NERFINISHED |
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: Dunfermline | Statement: [Firth of Forth basin, hasMajorCityOnEstuary, Dunfermline]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMajorCityOnEstuary Context triple: [Firth of Forth basin, hasMajorCityOnEstuary, Dunfermline]
-
A.
hasCityOnEstuary
Indicates that a city is located on or adjacent to the estuary of a river.
-
B.
hasMajorCityOnBasin
chosen
Indicates that a major city is located on or within the drainage basin of a specified water system.
-
C.
hasEstuaryNear
Indicates that the estuary of a water body is located in close proximity to a specified place or feature.
-
D.
hasEstuaryAt
Indicates that a river or watercourse flows into and meets a larger body of water (such as a sea, ocean, or lake) at a specific location.
-
E.
hasEstuaryWith
Indicates that a river or watercourse flows into and forms an estuary with a particular 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_69e2fabb349881908a13a212a0221a63 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f453035f508190be83a3d521723acf |
completed | May 1, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69f44d6ef33081908f5d36ba1ae5f473 |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 18, 2026, 4:25 a.m.