Triple
T27782685
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cafe 80's |
E699374
|
entity |
| Predicate | operatesInTimeline |
P97182
|
FINISHED |
| Object | original 2015 timeline |
—
|
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: original 2015 timeline | Statement: [Cafe 80's, operatesInTimeline, original 2015 timeline]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatesInTimeline Context triple: [Cafe 80's, operatesInTimeline, original 2015 timeline]
-
A.
operatesAtTime
Indicates that an action, process, or system is functioning or active during a specified time or time interval.
-
B.
operatedDuring
Indicates that an action, process, or system was functioning or in operation throughout a specified time period or event.
-
C.
entersTimeline
Indicates that an entity begins to appear or be included at a specific point within a timeline or chronological sequence.
-
D.
operatesWithin
Indicates that one entity carries out its activities, functions, or operations inside the scope, boundaries, or jurisdiction defined by another entity.
-
E.
appearsInTimePeriod
chosen
Indicates that an entity is present, active, or occurs within a specified time period.
- 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_69ef6a4b5a9081909c9111396c2be3d2 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69fe163a41a0819098403b470e327d29 |
completed | May 8, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69fe1358db5c819092570814a37ef5bd |
completed | May 8, 2026, 4:46 p.m. |
Created at: April 27, 2026, 5:11 p.m.