Triple
T16584040
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hongcun |
E402906
|
entity |
| Predicate | waterSystemFeature |
P20923
|
FINISHED |
| Object | canals running through the village |
—
|
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: canals running through the village | Statement: [Hongcun, waterSystemFeature, canals running through the village]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waterSystemFeature Context triple: [Hongcun, waterSystemFeature, canals running through the village]
-
A.
waterFeature
chosen
Indicates the presence of a natural or artificial body or flow of water associated with the subject.
-
B.
waterType
Indicates the specific kind or category of water associated with an entity (e.g., fresh, salt, brackish).
-
C.
waterServiceType
Indicates the specific kind or category of water service provided or associated with an entity.
-
D.
waterInfrastructure
Indicates the existence, development, or management of systems and facilities that supply, store, treat, or distribute water between entities.
-
E.
isPartOfWaterSystem
Indicates that one entity is a component, segment, or subsystem within a larger water distribution, treatment, or management system.
- 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_69d88387363c8190a97a0c942130de97 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e35999f80c8190852fd4137bc45a80 |
completed | April 18, 2026, 10:14 a.m. |
| PD | Predicate disambiguation | batch_69e296a7d9d0819088555bca6c936e79 |
completed | April 17, 2026, 8:23 p.m. |
Created at: April 10, 2026, 5:16 a.m.