Triple
T1291891
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Loch Lomond |
E27564
|
entity |
| Predicate | hasBasinShape |
P3557
|
FINISHED |
| Object | long narrow glacial trough |
—
|
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: long narrow glacial trough | Statement: [Loch Lomond, hasBasinShape, long narrow glacial trough]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBasinShape Context triple: [Loch Lomond, hasBasinShape, long narrow glacial trough]
-
A.
basinType
chosen
Indicates the specific kind or classification of a basin associated with an entity (e.g., by form, function, or hydrological role).
-
B.
formsBasinWith
Indicates that one geographic feature combines with another to create or define a shared basin or catchment area.
-
C.
basinState
Indicates that a state contains or encompasses the drainage basin or watershed of a particular river or water system.
-
D.
basin
Indicates a geographic area where surface water drains into a common outlet, such as a river, lake, or ocean.
-
E.
locatedInBasin
Indicates that one geographical or hydrological feature lies within the drainage or catchment area of a specified basin.
- 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_69a496d4ec448190ad653b2590c46711 |
completed | March 1, 2026, 7:43 p.m. |
| NER | Named-entity recognition | batch_69a4c0d7d15081909d3af19b9297f1cc |
completed | March 1, 2026, 10:42 p.m. |
| PD | Predicate disambiguation | batch_69a4bee41ca08190b0ad6f7ea40c0b62 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:51 p.m.