Triple
T12278110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Comedians in Cars Getting Coffee |
E292643
|
entity |
| Predicate | moveToPlatformDate |
P103988
|
FINISHED |
| Object | 2018-01 |
—
|
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: 2018-01 | Statement: [Comedians in Cars Getting Coffee, moveToPlatformDate, 2018-01]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: moveToPlatformDate Context triple: [Comedians in Cars Getting Coffee, moveToPlatformDate, 2018-01]
-
A.
movedToCurrentDateBy
Indicates that something has been rescheduled, adjusted, or shifted so that it now occurs or is set on the current date by a particular agent or process.
-
B.
movedToCurrentDateYear
Indicates that an entity has been moved, updated, or adjusted so that its associated date now falls within the current calendar year.
-
C.
movementDate
Indicates the date on which a movement, transfer, or relocation event occurs.
-
D.
movesDataTo
Indicates that one entity transfers or relocates data from its current location or state to another location or state.
-
E.
dateRelativeToGregorian
Indicates how a given date is positioned or expressed in relation to the standard Gregorian calendar date.
- 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_69d6ab6856488190b5d31178d5015f8e |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d9261e1570819084bb4fdb44aa6aea |
completed | April 10, 2026, 4:32 p.m. |
| PD | Predicate disambiguation | batch_69d91c4d9a9c8190aeb7beaf9792d8f0 |
completed | April 10, 2026, 3:50 p.m. |
| PDg | Predicate description generation | batch_69d9261b7f088190b69fe6961015fce3 |
completed | April 10, 2026, 4:32 p.m. |
Created at: April 8, 2026, 9:52 p.m.