Triple
T9817130
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | McGill, Nevada |
E238435
|
entity |
| Predicate | waterSourceHistoric |
P90162
|
FINISHED |
| Object | company-built water system |
—
|
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: company-built water system | Statement: [McGill, Nevada, waterSourceHistoric, company-built water system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waterSourceHistoric Context triple: [McGill, Nevada, waterSourceHistoric, company-built water system]
-
A.
waterSource
Indicates that one entity serves as the source or provider of water for another entity.
-
B.
waterSourceDedicatedTo
Indicates that a particular water source is specifically allocated or reserved for a designated use, group, or purpose.
-
C.
waterSourceAfter
Indicates that one water source occurs, appears, or is accessed after another in time or sequence.
-
D.
waterOrigin
Indicates the source or starting location from which the water originates or is supplied.
-
E.
waterSourceType
Indicates the kind or category of source from which water is obtained.
- F. None of above. chosen
Provenance (4 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_69ca84dfde1481909f47c286d715f892 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb2f4a1548190a5afc5ee0d7da392 |
completed | April 2, 2026, 12:06 a.m. |
| PD | Predicate disambiguation | batch_69cd03e01ea881909a7d93fc3994ace5 |
completed | April 1, 2026, 11:39 a.m. |
| PDg | Predicate description generation | batch_69cd06abc9248190a506b64e9c516d03 |
completed | April 1, 2026, 11:51 a.m. |
Created at: March 30, 2026, 8:30 p.m.