Triple
T36102652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cairnholm Island |
E1044255
|
entity |
| Predicate | timeLoopType |
P24449
|
FINISHED |
| Object | daily reset |
—
|
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: daily reset | Statement: [Cairnholm Island, timeLoopType, daily reset]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeLoopType Context triple: [Cairnholm Island, timeLoopType, daily reset]
-
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.
timeLoopController
Indicates a controlling relationship where one entity manages, initiates, or regulates a repeating cycle of time or events affecting another entity.
-
C.
timeLoopGuardian
Indicates a role in which an entity protects, maintains, or oversees the integrity and continuity of a recurring or looping timeline.
-
D.
timeLoopResidence
Indicates that an entity resides or remains within a repeating, cyclical segment of time, experiencing the same temporal interval over and over.
-
E.
loopType
chosen
Indicates the specific kind or category of loop structure or iteration pattern used in a process or control flow.
- 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_69f76e338e2c8190b7f3bc68bec76349 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b3e2f3c08190be4fd1ae4fa1266d |
completed | May 3, 2026, 8:45 p.m. |
| PD | Predicate disambiguation | batch_69f7b1bcc47081909fe7d592ac69006c |
completed | May 3, 2026, 8:36 p.m. |
Created at: May 3, 2026, 4:08 p.m.