Triple
T13170571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sinagua culture |
E312963
|
entity |
| Predicate | usedWaterManagement |
P62654
|
FINISHED |
| Object | check dams |
—
|
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: check dams | Statement: [Sinagua culture, usedWaterManagement, check dams]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedWaterManagement Context triple: [Sinagua culture, usedWaterManagement, check dams]
-
A.
waterUse
Indicates the amount or manner in which water is consumed, utilized, or withdrawn by an entity or activity.
-
B.
hasWaterManagementStructure
chosen
Indicates that one entity possesses, contains, or is associated with a built feature used to control, store, convey, or manage water.
-
C.
hasWaterUse
Indicates a relationship where one entity utilizes or consumes water for a particular purpose, process, or function.
-
D.
managesWaterFrom
Indicates that one entity is responsible for controlling, directing, or handling water originating from another entity.
-
E.
waterManagementAuthority
Indicates that an entity has official responsibility for overseeing, regulating, or managing water resources, services, or infrastructure for a given area or 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_69d806ac3ee081909b2fd27d060aa974 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98cf054f88190b05ced98d5a22a62 |
completed | April 10, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69d98bc2c0c88190be357811aa8e828d |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:13 p.m.