Triple
T10519818
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aquia Creek |
E248134
|
entity |
| Predicate | hasConfluenceDirection |
P30196
|
FINISHED |
| Object | flows generally eastward to the Potomac River |
—
|
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: flows generally eastward to the Potomac River | Statement: [Aquia Creek, hasConfluenceDirection, flows generally eastward to the Potomac River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasConfluenceDirection Context triple: [Aquia Creek, hasConfluenceDirection, flows generally eastward to the Potomac River]
-
A.
containsDirectionOf
Indicates that one entity includes or encompasses the directional orientation or path associated with another entity.
-
B.
hasDirectionType
chosen
Indicates that something possesses or is associated with a specific type or category of direction.
-
C.
hasDirectionReference
Indicates that one entity specifies or points to a directional orientation or reference frame for another entity.
-
D.
isInDirectionOf
Indicates that one entity is oriented or positioned toward the direction in which another entity lies.
-
E.
hasDownstreamConfluence
Indicates that one watercourse or flow feature joins or merges into another at a point located further downstream.
- 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_69d381c4aa948190942e1d803143fb0e |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d509de0b3081909bec337aa8ff193e |
completed | April 7, 2026, 1:42 p.m. |
| PD | Predicate disambiguation | batch_69d4fb94fa10819091f585bab4379c6f |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:28 p.m.