Triple
T27217582
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ITVBe |
E681180
|
entity |
| Predicate | timeshiftServiceOf |
P19768
|
FINISHED |
| Object | ITVBe |
—
|
NE NERFINISHED |
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: ITVBe | Statement: [ITVBe, timeshiftServiceOf, ITVBe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeshiftServiceOf Context triple: [ITVBe, timeshiftServiceOf, ITVBe]
-
A.
timeShiftService
chosen
Indicates that a service is provided with a shifted or delayed time relative to its original or real-time schedule.
-
B.
timeShiftProperty
Indicates a relationship where one property value is derived from another by applying a temporal shift (e.g., offsetting it to an earlier or later point in time).
-
C.
timeTravelElement
Indicates that the situation, event, or narrative involves an element of time travel, such as moving between different points in time or altering temporal sequences.
-
D.
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.
-
E.
timeJump
Indicates a discontinuous transition of an entity from one point in time to another, skipping the intervening duration.
- 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_69eefac9f64c8190a07490fe0c8b72a3 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f6261e75908190810516f49032aae1 |
completed | May 2, 2026, 4:28 p.m. |
| PD | Predicate disambiguation | batch_69f623a91b9c8190b2e2fdbc55cb89b6 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 9:41 a.m.