Triple
T8597732
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Loch Einich |
E203592
|
entity |
| Predicate | hasOutflowDirection |
P49386
|
FINISHED |
| Object | north |
—
|
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: north | Statement: [Loch Einich, hasOutflowDirection, north]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOutflowDirection Context triple: [Loch Einich, hasOutflowDirection, north]
-
A.
hasDirectionFrom
chosen
Indicates that one entity has a specific orientation or directional relationship when referenced from another entity.
-
B.
flowsFrom
Indicates that a substance, medium, or influence moves or originates from one entity or location and proceeds outward to another.
-
C.
dataFlowDirection
Indicates the direction in which data moves or is transmitted from a source entity to a target entity.
-
D.
flowsTo
Indicates that something moves or is directed from one location or entity toward and into another, typically in a continuous or channel-like manner.
-
E.
flowsAt
Indicates that a fluid or substance moves through or along a specific location, point, or region.
- 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_69ca832b56948190ba751cec255308f1 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cc46cacbe88190b95beeedc9f480b0 |
completed | March 31, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69cc454504448190aaad2af8b17357cd |
completed | March 31, 2026, 10:05 p.m. |
Created at: March 30, 2026, 6:24 p.m.