Triple
T1270287
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paterson River |
E15692
|
entity |
| Predicate | flowsInDirection |
P19752
|
FINISHED |
| Object | generally south |
—
|
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: generally south | Statement: [Paterson River, flowsInDirection, generally south]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: flowsInDirection Context triple: [Paterson River, flowsInDirection, generally south]
-
A.
flowsAt
Indicates that a fluid or substance moves through or along a specific location, point, or region.
-
B.
flowsFrom
Indicates that a substance, medium, or influence moves or originates from one entity or location and proceeds outward to another.
-
C.
flowsGenerallyDirection
chosen
Indicates that something typically moves or progresses in a particular overall direction, without requiring an exact or constant path.
-
D.
dataFlowDirection
Indicates the direction in which data moves or is transmitted from a source entity to a target entity.
-
E.
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.
- 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_69a4935a94308190bb92555b79032824 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4c0691d70819088e57c78ff34af1e |
completed | March 1, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69a4bede52a081909665d60acbe41d31 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:50 p.m.