Triple
T26194575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Banpo Bridge Rainbow Fountain |
E655061
|
entity |
| Predicate | waterPumpedFrom |
P4102
|
FINISHED |
| Object | Han 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: Han River | Statement: [Banpo Bridge Rainbow Fountain, waterPumpedFrom, Han River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waterPumpedFrom Context triple: [Banpo Bridge Rainbow Fountain, waterPumpedFrom, Han River]
-
A.
waterVolume
Indicates the amount of water present in or associated with an entity, typically measured as a volume.
-
B.
waterFunction
Indicates that one entity serves a particular role, purpose, or function in relation to water (e.g., how it uses, manages, affects, or interacts with water).
-
C.
waterSource
chosen
Indicates that one entity serves as the source or provider of water for another entity.
-
D.
waterDivertedFrom
Indicates that water is intentionally redirected or channeled away from one source, path, or location to another.
-
E.
waterDivertedThrough
Indicates that the flow of water is intentionally redirected from its original course to pass through a specified structure, channel, or location.
- 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_69ee5b48236c81908fe385b6afc4f60b |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f650c70d7c819093d9a0f005f7c8d5 |
completed | May 2, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69f64cab1f648190a2a9460690d18a37 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 26, 2026, 8:45 p.m.