Triple
T32505546
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mantua, Utah |
E830782
|
entity |
| Predicate | recreationalUseOfMantuaReservoir |
P40334
|
FINISHED |
| Object | fishing |
—
|
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: fishing | Statement: [Mantua, Utah, recreationalUseOfMantuaReservoir, fishing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recreationalUseOfMantuaReservoir Context triple: [Mantua, Utah, recreationalUseOfMantuaReservoir, fishing]
-
A.
reservoirUse
chosen
Indicates the way a reservoir is utilized or the purpose for which its stored water is used.
-
B.
usesReservoir
Indicates that one entity draws upon, depends on, or operates using a particular reservoir as a resource or source.
-
C.
isRecreationalLake
Indicates that a lake is primarily used for recreational activities such as swimming, boating, or fishing rather than for industrial or purely natural purposes.
-
D.
reservoir
Indicates that one entity serves as a storage or containment source (often for a resource) that can supply or affect another entity.
-
E.
reservoirAlsoKnownAs
Indicates that a reservoir is referred to by an alternative name or alias.
- 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_69f349219cb8819087e120f509629c1b |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c44b26a88190be979e894c7dfd38 |
completed | May 3, 2026, 3:43 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2a14b081908162923dfbf0a6f4 |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 1 a.m.