Triple
T3377625
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eye of Harmony |
E71103
|
entity |
| Predicate | temporalEffect |
P48090
|
FINISHED |
| Object | enables controlled time travel |
—
|
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: enables controlled time travel | Statement: [Eye of Harmony, temporalEffect, enables controlled time travel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: temporalEffect Context triple: [Eye of Harmony, temporalEffect, enables controlled time travel]
-
A.
temporalAspect
Indicates the time-related characteristics or phase (such as duration, frequency, or temporal status) associated with an event or relationship.
-
B.
effectDuration
Indicates the length of time for which an effect remains active or valid.
-
C.
effectOnSchedule
Indicates how an event, action, or condition changes, disrupts, or influences a planned schedule or timeline.
-
D.
tempo
Indicates the speed or pace at which an action, process, or sequence unfolds over time.
-
E.
timeDependence
Indicates that one entity’s state, value, or behavior is determined by or varies as a function of another entity over time.
- 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_69ad85a7f80c8190a05e43013f298942 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb2e8d1988190b6fb6c4c5502f25f |
completed | March 8, 2026, 5:33 p.m. |
| PD | Predicate disambiguation | batch_69ada433059881908e46f38cc5f40a32 |
completed | March 8, 2026, 4:30 p.m. |
| PDg | Predicate description generation | batch_69adaa518ac88190b64f949ace018ab7 |
completed | March 8, 2026, 4:56 p.m. |
Created at: March 8, 2026, 3:13 p.m.