Triple
T16584042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hongcun |
E402906
|
entity |
| Predicate | waterSystemFunction |
P39319
|
FINISHED |
| Object | domestic water supply |
—
|
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: domestic water supply | Statement: [Hongcun, waterSystemFunction, domestic water supply]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waterSystemFunction Context triple: [Hongcun, waterSystemFunction, domestic water supply]
-
A.
waterInfrastructure
Indicates the existence, development, or management of systems and facilities that supply, store, treat, or distribute water between entities.
-
B.
waterServiceType
chosen
Indicates the specific kind or category of water service provided or associated with an entity.
-
C.
waterDistributionMethod
Indicates how water is delivered, supplied, or allocated from a source to its intended recipients or locations.
-
D.
waterType
Indicates the specific kind or category of water associated with an entity (e.g., fresh, salt, brackish).
-
E.
waterInfrastructureRole
Indicates the functional role or involvement an entity has in the provision, management, or operation of water infrastructure systems.
- 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.