Triple
T27868497
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Einstein |
E704425
|
entity |
| Predicate | timeTravelDurationSubjective |
P165105
|
FINISHED |
| Object | 1 minute |
—
|
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: 1 minute | Statement: [Einstein, timeTravelDurationSubjective, 1 minute]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeTravelDurationSubjective Context triple: [Einstein, timeTravelDurationSubjective, 1 minute]
-
A.
timeTravelType
Indicates the specific method or mechanism by which time travel is carried out in a given context.
-
B.
timeTravelInvolvement
Indicates that an entity participates in, is affected by, or is otherwise involved in an instance of time travel.
-
C.
timeTravelDirection
Indicates the temporal direction in which time travel occurs, such as moving into the past or into the future.
-
D.
timeTravelTo
Indicates traveling from one point in time to another, typically different, point in time.
-
E.
timeTravelMethod
Indicates the specific mechanism or technique by which an entity performs or experiences time travel.
- F. None of above. chosen
Provenance (4 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_69ef840f12408190b539d00d79658abf |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f65705a3048190a3728b695ba2ae65 |
completed | May 2, 2026, 7:56 p.m. |
| PD | Predicate disambiguation | batch_69f651a931748190a637e631a52bbfaa |
completed | May 2, 2026, 7:34 p.m. |
| PDg | Predicate description generation | batch_69f6562ef4e4819082ce6abd41b74dc5 |
completed | May 2, 2026, 7:53 p.m. |
Created at: April 27, 2026, 6:22 p.m.