Triple
T30932775
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scranton branch |
E788040
|
entity |
| Predicate | portrayedInStyle |
P121907
|
FINISHED |
| Object | mockumentary |
—
|
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: mockumentary | Statement: [Scranton branch, portrayedInStyle, mockumentary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: portrayedInStyle Context triple: [Scranton branch, portrayedInStyle, mockumentary]
-
A.
inTheStyleOf
chosen
Indicates that one entity is created, performed, or presented in a manner that imitates or closely resembles the characteristic style of another entity.
-
B.
conveysStyle
Indicates that one entity expresses, communicates, or embodies a particular style through its form, behavior, or presentation.
-
C.
governsInStyle
Indicates that a governing entity exercises authority or leadership in a distinctive, notable, or characteristic manner.
-
D.
personHasNotableStyle
Indicates that a person is recognized for having a distinctive or noteworthy style.
-
E.
styledCelebrity
Indicates that one entity (typically a stylist or source) is responsible for selecting or creating the fashion or appearance of a celebrity.
- 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_69fdb45537288190b6791078d4a6899f |
completed | May 8, 2026, 10 a.m. |
| PD | Predicate disambiguation | batch_69fdb39ad96481908376d7def9fafc13 |
completed | May 8, 2026, 9:57 a.m. |
Created at: April 29, 2026, 8:52 p.m.