Triple
T11990745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hugh Apiston |
E285397
|
entity |
| Predicate | livesInTimeLoop |
P66525
|
FINISHED |
| Object | Cairnholm time loop |
—
|
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: Cairnholm time loop | Statement: [Hugh Apiston, livesInTimeLoop, Cairnholm time loop]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: livesInTimeLoop Context triple: [Hugh Apiston, livesInTimeLoop, Cairnholm time loop]
-
A.
hasTemporalParadox
Indicates that a situation, event, or sequence of events involves a contradiction or inconsistency in time, such as conflicting timelines or causality loops.
-
B.
usesTimeTravelFor
Indicates a relationship where an entity employs time travel as a means or method to achieve, affect, or interact with another entity or objective.
-
C.
timeLoopMechanism
chosen
Indicates a relationship where events or states are repeatedly reset or cycled through the same temporal sequence due to a mechanism that loops time.
-
D.
timeExistence
Indicates the period or duration during which an entity exists or is valid.
-
E.
timeTravelDeviceUsed
Indicates that an entity makes use of a device or mechanism that enables travel through 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_69d6ab44a77c8190a652f4b27164e4ef |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d903afe4388190a2cf2328e85adf9b |
completed | April 10, 2026, 2:05 p.m. |
| PD | Predicate disambiguation | batch_69d902abca70819098291aa51b593708 |
completed | April 10, 2026, 2:01 p.m. |
Created at: April 8, 2026, 9:46 p.m.