Triple
T13610228
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central Perk |
E325167
|
entity |
| Predicate | setTimePeriodFictional |
P106751
|
FINISHED |
| Object | 1990s |
—
|
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: 1990s | Statement: [Central Perk, setTimePeriodFictional, 1990s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: setTimePeriodFictional Context triple: [Central Perk, setTimePeriodFictional, 1990s]
-
A.
fictionalTime
Indicates that the associated time or temporal reference exists only within a fictional or imagined context, rather than in real-world chronology.
-
B.
fictionalTimeDepth
chosen
Indicates a relationship where an entity is associated with a time period or temporal depth that exists only within a fictional or imagined context.
-
C.
setInFictionalYear
Indicates that the events or narrative of a work are situated in a specified fictional or non-real calendar year.
-
D.
fictionalEra
Indicates the time period or age within a fictional or imaginary setting in which an entity exists or an event occurs.
-
E.
fictionalTraditionDuration
Indicates the length of time a fictional tradition has existed or is observed.
- 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_69d8076aae28819092cf636190ee5529 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbbb9ee3f081909056dc1a92c40b7a |
completed | April 12, 2026, 3:34 p.m. |
| PD | Predicate disambiguation | batch_69dbae1b3ee481909bd43ded6227a3e5 |
completed | April 12, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:50 p.m.