Triple
T11990789
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Horace Somnusson |
E285398
|
entity |
| Predicate | timeLoopResidence |
P102756
|
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: [Horace Somnusson, timeLoopResidence, Cairnholm time loop]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeLoopResidence Context triple: [Horace Somnusson, timeLoopResidence, Cairnholm time loop]
-
A.
timeLoopMechanism
Indicates a relationship where events or states are repeatedly reset or cycled through the same temporal sequence due to a mechanism that loops time.
-
B.
hasResidenceTime
Indicates the duration for which something remains or stays within a particular place, system, or state.
-
C.
timeLoopController
Indicates a controlling relationship where one entity manages, initiates, or regulates a repeating cycle of time or events affecting another entity.
-
D.
locationPeriod
Indicates that an entity is associated with being at a particular location during a specified time period.
-
E.
timePeriod
Indicates the specific span or interval of time during which an event, state, or relationship occurs or is valid.
- 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_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. |
| PDg | Predicate description generation | batch_69d903a8695c8190bfa9d7ca50834f9f |
completed | April 10, 2026, 2:05 p.m. |
Created at: April 8, 2026, 9:46 p.m.