Triple
T14253700
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Time Lock |
E353331
|
entity |
| Predicate | temporalDirection |
P61649
|
FINISHED |
| Object | typically blocks changes from both past and future |
—
|
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: typically blocks changes from both past and future | Statement: [Time Lock, temporalDirection, typically blocks changes from both past and future]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: temporalDirection Context triple: [Time Lock, temporalDirection, typically blocks changes from both past and future]
-
A.
temporalAspect
Indicates the time-related characteristics or phase (such as duration, frequency, or temporal status) associated with an event or relationship.
-
B.
temporal
Indicates a relationship that situates one event, state, or entity in time relative to another (e.g., before, after, or during).
-
C.
temporality
Indicates the time-related relationship between events or states, such as their order, duration, or simultaneity.
-
D.
timeTravelDirection
chosen
Indicates the temporal direction in which time travel occurs, such as moving into the past or into the future.
-
E.
temporalRelation
Indicates a relationship that specifies how two events or states are positioned relative to each other in time (e.g., before, after, or overlapping).
- 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_69d8278c43e08190824146f4632b89a5 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de6297f38c819090d7c7fd8bfa2e9e |
completed | April 14, 2026, 3:51 p.m. |
| PD | Predicate disambiguation | batch_69de05c09b7881908acbca18bd7d997c |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 1:09 a.m.