Triple
T417534
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jianghan Plain |
E8026
|
entity |
| Predicate | floodControlInfrastructure |
P7637
|
FINISHED |
| Object | dikes |
—
|
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: dikes | Statement: [Jianghan Plain, floodControlInfrastructure, dikes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: floodControlInfrastructure Context triple: [Jianghan Plain, floodControlInfrastructure, dikes]
-
A.
waterInfrastructure
Indicates the existence, development, or management of systems and facilities that supply, store, treat, or distribute water between entities.
-
B.
hasFloodProtectionProject
chosen
Indicates that a flood protection project exists or is implemented for the referenced entity.
-
C.
hasFloodRisk
Indicates that an entity is exposed to a potential or expected risk of flooding under certain conditions.
-
D.
hasStructureOnWatercourse
Indicates that a structure is physically located on, over, or directly associated with a specific watercourse.
-
E.
waterwaySystem
Indicates that one entity is part of, or belongs to, a connected network of waterways associated with 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_69a2e7f1d1bc81909cf2dc9754a3c334 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2eebde1d881908fb212bfba9d7c67 |
completed | Feb. 28, 2026, 1:33 p.m. |
| PD | Predicate disambiguation | batch_69a2edd1ca148190a66bd8c5aad867d5 |
completed | Feb. 28, 2026, 1:29 p.m. |
Created at: Feb. 28, 2026, 1:11 p.m.