Triple
T20872259
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Breakneck Ridge Trail |
E513921
|
entity |
| Predicate | approximateActivityTime |
P125927
|
FINISHED |
| Object | half-day hike |
—
|
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: half-day hike | Statement: [Breakneck Ridge Trail, approximateActivityTime, half-day hike]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateActivityTime Context triple: [Breakneck Ridge Trail, approximateActivityTime, half-day hike]
-
A.
activityTime
Indicates the time period during which an activity occurs or is scheduled to take place.
-
B.
endTimeApproximate
Indicates that the recorded end time of an event or action is not exact but an approximate value.
-
C.
timeStartApprox
Indicates that the associated event or state begins at an approximate, rather than exact, point in time.
-
D.
intendedDuration
Indicates the planned or expected length of time for which an action, event, or state is meant to occur or remain in effect.
-
E.
timeframeApproximate
chosen
Indicates that the time period associated with an event or relation is not exact but only roughly or loosely specified.
- 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_69e0b4f675cc8190b4e745225b62eb66 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c465693881909fe4c756ddc4f291 |
completed | April 21, 2026, 12:27 a.m. |
| PD | Predicate disambiguation | batch_69e5c9a593f481908beb457c29f1ce73 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:45 p.m.