Triple
T32936014
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lone Oak picnic area |
E842528
|
entity |
| Predicate | typicalUseHours |
P70126
|
FINISHED |
| Object | daytime |
—
|
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: daytime | Statement: [Lone Oak picnic area, typicalUseHours, daytime]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalUseHours Context triple: [Lone Oak picnic area, typicalUseHours, daytime]
-
A.
typicalUseDays
Indicates the usual or expected number of days over which something is used or intended to be used.
-
B.
hasTypicalUseTime
chosen
Indicates the usual or expected duration or time period during which something is commonly used or in operation.
-
C.
typicalConsumption
Indicates the usual or characteristic amount or pattern in which one entity consumes or uses another.
-
D.
recommendedUsageTime
Indicates the period of time for which something is advised or intended to be used.
-
E.
powerUse
Indicates the amount or manner in which one entity consumes or utilizes power or energy in relation to another entity 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_69f34949727c81909d195c97de3341c8 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a0379f0cbe481909b4b8fc6cbe297f0 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:20 a.m.