Triple
T35142555
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Smelly Cat |
E1014732
|
entity |
| Predicate | performedAtFictionalLocation |
P198402
|
FINISHED |
| Object | Central Perk |
—
|
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: Central Perk | Statement: [Smelly Cat, performedAtFictionalLocation, Central Perk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performedAtFictionalLocation Context triple: [Smelly Cat, performedAtFictionalLocation, Central Perk]
-
A.
basedInFictionalLocation
Indicates that an entity’s primary setting, origin, or operations occur in a fictional (non-real) location.
-
B.
locatedInFictionalEvent
Indicates that one entity (typically a place, object, or character) exists or occurs within the context or setting of a fictional event.
-
C.
worksAtFictionalPlace
Indicates that an entity is employed at or associated with performing work in a fictional or imaginary location.
-
D.
basedInFictionalWorkLocation
Indicates that an entity’s location or setting is situated within a fictional place as depicted in a specific creative work.
-
E.
hasBranchInFictionalLocation
Indicates that an organization maintains a branch, office, or presence within a fictional or imaginary location.
- 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_69f76dda7c108190a2ffd93eb6c341a7 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fee0b2da3c8190a3519d0564f2f32d |
completed | May 9, 2026, 7:22 a.m. |
| PD | Predicate disambiguation | batch_69fee05b315c819081dfcbfb15273487 |
completed | May 9, 2026, 7:20 a.m. |
| PDg | Predicate description generation | batch_69fee0b03a0c81909117dc5915d77295 |
completed | May 9, 2026, 7:22 a.m. |
Created at: May 3, 2026, 4:02 p.m.