Triple
T4015840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spicket River |
E90754
|
entity |
| Predicate | flowsGenerallyToward |
P19752
|
FINISHED |
| Object | southeast |
—
|
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: southeast | Statement: [Spicket River, flowsGenerallyToward, southeast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: flowsGenerallyToward Context triple: [Spicket River, flowsGenerallyToward, southeast]
-
A.
flowsMostly
Indicates that one entity predominantly flows or moves in the direction of, or through, another entity, more so than in other directions or paths.
-
B.
flowsGenerallyDirection
chosen
Indicates that something typically moves or progresses in a particular overall direction, without requiring an exact or constant path.
-
C.
flowsAcross
Indicates that one entity moves or extends in a continuous stream from one side of another entity to the other, traversing its area or boundary.
-
D.
flowsUnder
Indicates that one entity (typically a river, stream, or liquid) passes beneath another entity (such as a bridge, structure, or obstacle) along its course.
-
E.
flowType
Indicates the kind or category of flow (such as direction, pattern, or mode of movement/transfer) that characterizes the relationship between entities.
- 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_69aed95e44088190aff7d90a151b1b20 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefaec08dc8190a341809059554f84 |
completed | March 9, 2026, 4:53 p.m. |
| PD | Predicate disambiguation | batch_69aef8fa6fec81909b1190ecbba61410 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:35 p.m.