Triple
T17101652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | River Lossie |
E414993
|
entity |
| Predicate | flowsNorthward |
P125930
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [River Lossie, flowsNorthward, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: flowsNorthward Context triple: [River Lossie, flowsNorthward, true]
-
A.
flowsNorthwardThrough
Indicates that something, typically a river or current, moves in a generally northward direction while passing through a specified area or region.
-
B.
flowsNorthOf
Indicates that one entity (typically a watercourse or current) moves in a generally northward direction while remaining geographically north of the other entity.
-
C.
flowsNorthwardsTo
Indicates that something moves or is directed in a generally northward direction until it reaches or connects with another specified entity.
-
D.
flowsNorthFrom
Indicates that something moves or travels in a generally northward direction starting from a specified origin.
-
E.
flowsNorthwestToward
Indicates movement or progression in a generally northwest direction toward a specified target or destination.
- F. None of above. chosen
Provenance (4 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_69d886cfc8e88190b05ba466edd35591 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dc239a088190a776fe0f4361ffc7 |
completed | April 18, 2026, 7:31 p.m. |
| PD | Predicate disambiguation | batch_69e35d6b1b988190a8d6b6fe78c35e59 |
completed | April 18, 2026, 10:31 a.m. |
| PDg | Predicate description generation | batch_69e37542d060819082aa73948eb8ebd4 |
completed | April 18, 2026, 12:12 p.m. |
Created at: April 10, 2026, 5:35 a.m.