Triple
T17159217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fish Lake Valley Hot Well |
E416430
|
entity |
| Predicate | typicalUsePattern |
P12995
|
FINISHED |
| Object | day use |
—
|
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: day use | Statement: [Fish Lake Valley Hot Well, typicalUsePattern, day use]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalUsePattern Context triple: [Fish Lake Valley Hot Well, typicalUsePattern, day use]
-
A.
usagePattern
chosen
Indicates how something is typically used or the recurring manner in which it is employed or consumed.
-
B.
typicalUsagePhase
Indicates the phase or stage in which something is most commonly or characteristically used.
-
C.
operatingPattern
Indicates the characteristic way in which an entity functions or operates over time, such as its typical mode, schedule, or behavioral pattern.
-
D.
typicalUsageFormat
Indicates the usual or standard way in which something is expressed, presented, or formatted in practice.
-
E.
hasTypicalUseContext
Indicates that something is commonly or characteristically used within a particular situation, setting, or context.
- 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_69d886d279c081909f8ff1f743ddeb69 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3f9103e3881908e76cea1c4880779 |
completed | April 18, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69e3830d2a90819092386717dc56f0e8 |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:37 a.m.