Triple
T12996497
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aron Ralston |
E322047
|
entity |
| Predicate | timeTrapped |
P63872
|
FINISHED |
| Object | about 127 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: about 127 hours | Statement: [Aron Ralston, timeTrapped, about 127 hours]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeTrapped Context triple: [Aron Ralston, timeTrapped, about 127 hours]
-
A.
trappedDuring
chosen
Indicates that one entity is confined, caught, or immobilized while a specified event or situation is occurring.
-
B.
timeBehind
Indicates that one entity occurs or is positioned later in time than another, lagging behind it on a temporal scale.
-
C.
timeInTomb
Indicates the duration that an entity remains or has remained inside a tomb.
-
D.
timeLimited
Indicates that the relationship or action is constrained to occur or remain valid only within a specific, limited time period.
-
E.
time
Indicates a temporal relationship specifying when an event occurs or how entities are ordered or related in time.
- 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_69d8076479b8819090afce3591939cdf |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97e7980288190a9fe629a8cc76a52 |
completed | April 10, 2026, 10:49 p.m. |
| PD | Predicate disambiguation | batch_69d97dc153a081909d13a694993f074a |
completed | April 10, 2026, 10:46 p.m. |
Created at: April 9, 2026, 8:45 p.m.