Triple
T5408417
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Three Peaks Challenge |
E120949
|
entity |
| Predicate | typicalTimeLimit |
P7618
|
FINISHED |
| Object | 24 hours |
—
|
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: 24 hours | Statement: [National Three Peaks Challenge, typicalTimeLimit, 24 hours]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalTimeLimit Context triple: [National Three Peaks Challenge, typicalTimeLimit, 24 hours]
-
A.
typicalTimes
Indicates the usual or characteristic times at which an event, activity, or condition typically occurs.
-
B.
timeLimited
Indicates that the relationship or action is constrained to occur or remain valid only within a specific, limited time period.
-
C.
typicalDurationDays
chosen
Indicates the usual or expected number of days that an associated event, process, or state typically lasts.
-
D.
typicalTestDuration
Indicates the usual or expected length of time required to complete a given test.
-
E.
intendedDuration
Indicates the planned or expected length of time for which an action, event, or state is meant to occur or remain in effect.
- 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_69bd46391c0c81909fa484446732b6a3 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd8794e0c4819082bebf2da5e41201 |
completed | March 20, 2026, 5:44 p.m. |
| PD | Predicate disambiguation | batch_69bd8467e6b48190b9eaa9de67072e06 |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:05 p.m.