Triple
T30933026
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World's Best Boss mug |
E788045
|
entity |
| Predicate | typicalLocationInShow |
P55519
|
FINISHED |
| Object | Michael Scott's desk |
—
|
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: Michael Scott's desk | Statement: [World's Best Boss mug, typicalLocationInShow, Michael Scott's desk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalLocationInShow Context triple: [World's Best Boss mug, typicalLocationInShow, Michael Scott's desk]
-
A.
plotLocation
Indicates the relationship between a creative work and the place or setting where its story or events occur.
-
B.
notableShowLocation
Indicates that a show or performance is notably associated with, took place at, or is best known for occurring in a particular location.
-
C.
fictionalTryoutLocationInSeries
Indicates the location where a fictional tryout event takes place within a specific series.
-
D.
primaryLocationOfAppearances
chosen
Indicates the main place where an entity most frequently appears or is featured.
-
E.
crewLocation
Indicates that a crew is located at, assigned to, or present in a specific place or environment.
- 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_69f224c0b7fc819090cb89df60d23653 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e2fac0819089b522db3260028c |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 8:52 p.m.