Triple
T23355195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hatchōbori |
E593022
|
entity |
| Predicate | hasRiverOrCanalNearby |
P165
|
FINISHED |
| Object | Sumida River |
—
|
NE NERFINISHED |
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: Sumida River | Statement: [Hatchōbori, hasRiverOrCanalNearby, Sumida River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRiverOrCanalNearby Context triple: [Hatchōbori, hasRiverOrCanalNearby, Sumida River]
-
A.
hasNearbyRiverStructure
Indicates that a river-related structure (such as a dam, bridge, or levee) is located close to the referenced entity.
-
B.
hasRiver
chosen
Indicates that a location or area contains, is traversed by, or is directly associated with a river.
-
C.
nearbyCanal
Indicates that one entity is located close to or in the immediate vicinity of a canal.
-
D.
locatedInRiverArea
Indicates that one entity is situated within the geographic area occupied by, adjacent to, or directly associated with a particular river.
-
E.
hasNearbyWater
Indicates that one entity is located close to a body of water associated with or relevant to another entity.
- 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_69e25d24d2a4819092e6ede74c2a918d |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f19a169bb88190a2ca659fce1133e5 |
completed | April 29, 2026, 5:41 a.m. |
| PD | Predicate disambiguation | batch_69effcfd8d288190937a887fe6023c11 |
completed | April 28, 2026, 12:19 a.m. |
Created at: April 17, 2026, 5:25 p.m.