Triple
T6140238
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Forrest J Ackerman |
E136941
|
entity |
| Predicate | roleInFandom |
P40776
|
FINISHED |
| Object | prominent science fiction fan |
—
|
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: prominent science fiction fan | Statement: [Forrest J Ackerman, roleInFandom, prominent science fiction fan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInFandom Context triple: [Forrest J Ackerman, roleInFandom, prominent science fiction fan]
-
A.
fandomContext
chosen
Indicates that the relationship or action occurs specifically within the context of a particular 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.
roleInStories
Indicates the specific function, position, or character part an entity plays within one or more stories.
-
D.
fictionalUniverseRole
Indicates the role or function an entity has within a particular fictional universe or narrative setting.
-
E.
fandomFocus
Indicates that one entity is primarily centered on, dedicated to, or concerned with the fan community or fan-related aspects of another entity.
- 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_69c008a179388190a3b5a081bbf46d55 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c05cb030fc8190b78e4967eea65611 |
completed | March 22, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69c055f19b0c81908be34a00ab218723 |
completed | March 22, 2026, 8:49 p.m. |
Created at: March 22, 2026, 4:15 p.m.