Triple
T8820055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harlem Creek (historic) |
E209878
|
entity |
| Predicate | flowedThrough |
P11198
|
FINISHED |
| Object | northern Manhattan landscape |
—
|
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: northern Manhattan landscape | Statement: [Harlem Creek (historic), flowedThrough, northern Manhattan landscape]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: flowedThrough Context triple: [Harlem Creek (historic), flowedThrough, northern Manhattan landscape]
-
A.
flowsAt
Indicates that a fluid or substance moves through or along a specific location, point, or region.
-
B.
isPassedThroughBy
chosen
Indicates that something serves as a medium, route, or channel through which another thing moves, flows, or is transmitted.
-
C.
flownWhen
Indicates that one entity has been flown or transported at a specific time or under certain temporal conditions associated with another entity.
-
D.
flowsOver
Indicates that one substance or medium moves across the surface or boundary of another, covering or passing above it.
-
E.
fundsFlowThrough
Indicates that financial resources are transferred or routed from one entity to another via an intermediate entity, account, or channel.
- 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_69ca8364e13081909c85fe80f44fe86f |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc600fbbac8190ad36d93fff60a33f |
completed | April 1, 2026, midnight |
| PD | Predicate disambiguation | batch_69cc5c21e64c81908490e3b0875dc0d6 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:46 p.m.