Triple
T751069
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Weeping Angels |
E15447
|
entity |
| Predicate | timeTravelMechanism |
P3705
|
FINISHED |
| Object | Temporal displacement via touch |
—
|
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: Temporal displacement via touch | Statement: [Weeping Angels, timeTravelMechanism, Temporal displacement via touch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeTravelMechanism Context triple: [Weeping Angels, timeTravelMechanism, Temporal displacement via touch]
-
A.
timeTravelTo
Indicates traveling from one point in time to another, typically different, point in time.
-
B.
timeTravelFrom
Indicates a relationship where an entity initiates time travel starting from a specific time or temporal location.
-
C.
timeExistence
Indicates the period or duration during which an entity exists or is valid.
-
D.
transitionMechanismUsedWith
chosen
Indicates that a particular transition or change from one state to another is carried out using a specified mechanism or method.
-
E.
timescale
Indicates the temporal scale or duration over which a process, relationship, or effect occurs or is evaluated.
- 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_69a493599a0081908da65f3407af1ef2 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a64c67748190aef3522b4b428563 |
completed | March 1, 2026, 8:49 p.m. |
| PD | Predicate disambiguation | batch_69a4a501c4cc81908de6d63e3d4f60d7 |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.