Triple
T28039194
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Viking Graben |
E708490
|
entity |
| Predicate | hasNeighboringBasin |
P173221
|
FINISHED |
| Object | Moray Firth Basin |
—
|
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: Moray Firth Basin | Statement: [Viking Graben, hasNeighboringBasin, Moray Firth Basin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNeighboringBasin Context triple: [Viking Graben, hasNeighboringBasin, Moray Firth Basin]
-
A.
isLocatedNearBasin
chosen
Indicates that one entity is situated close to or in the immediate vicinity of a basin.
-
B.
hasWaterBasins
Indicates that one entity possesses, contains, or includes one or more water basins in relation to another entity.
-
C.
hasNeighboringValley
Indicates that one geographic feature, typically a valley, is directly adjacent to or borders another valley.
-
D.
hasBasinFunction
Indicates that something serves the role or performs the function of a basin, such as collecting, holding, or draining water or other substances.
-
E.
hasBasinNamed
Indicates that an entity possesses or is associated with a basin that has a specified name.
- 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_69ef9b6cf538819094a633ffa67afec1 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69fd592e48cc81909d754cc6c4bd99ae |
completed | May 8, 2026, 3:31 a.m. |
| PD | Predicate disambiguation | batch_69fd58b7f9b881909dc099b28d567784 |
completed | May 8, 2026, 3:30 a.m. |
Created at: April 27, 2026, 8:23 p.m.