Triple
T26114404
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Psych-O's |
E658781
|
entity |
| Predicate | fandomOfCharacter |
P91126
|
FINISHED |
| Object | Shawn Spencer |
—
|
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: Shawn Spencer | Statement: [Psych-O's, fandomOfCharacter, Shawn Spencer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fandomOfCharacter Context triple: [Psych-O's, fandomOfCharacter, Shawn Spencer]
-
A.
fandomCharacteristic
Indicates that an entity possesses a particular trait, behavior, or quality specifically in the context of its fandom or fan community.
-
B.
fandomType
Indicates the specific category or kind of fandom relationship that exists between an entity and the subject of that fandom.
-
C.
fandomFocus
Indicates that one entity is primarily centered on, dedicated to, or concerned with the fan community or fan-related aspects of another entity.
-
D.
subjectOfFandom
chosen
Indicates that one entity is the focus or object of another entity’s fandom, admiration, or devoted interest.
-
E.
fandomScope
Indicates the extent or boundaries of a fandom-related relationship, such as how broadly or narrowly a fan’s interest, participation, or recognition applies.
- 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_69ee5bc20298819099a42be042eb2349 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f60ac643108190ae81561267155791 |
completed | May 2, 2026, 2:31 p.m. |
| PD | Predicate disambiguation | batch_69f5f7fd90fc81909055b211368f9139 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 8:04 p.m.