Triple
T33083978
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FlashForward (TV series) |
E846583
|
entity |
| Predicate | hasFandomAbbreviation |
P68021
|
FINISHED |
| Object | FF |
—
|
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: FF | Statement: [FlashForward (TV series), hasFandomAbbreviation, FF]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFandomAbbreviation Context triple: [FlashForward (TV series), hasFandomAbbreviation, FF]
-
A.
hasFanAbbreviation
chosen
Indicates that an entity is associated with an abbreviation or short form commonly used by fans to refer to it.
-
B.
hasFandomAssociation
Indicates a relationship where an entity is associated with, connected to, or recognized within a particular fandom or fan community.
-
C.
hasFandomDesignation
Indicates that an entity has a specific name or label used by its fan community to refer to it or its fandom.
-
D.
fandomNickname
Indicates that one entity is the nickname used by fans to refer to another entity (such as a person, group, or work).
-
E.
hasFandomElement
Indicates that something includes, features, or is associated with an element derived from or related to a fandom.
- 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_69f34954d46c8190a04a159cc5f99efd |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd509e6bc08190b263923c2f40fea3 |
completed | May 8, 2026, 2:55 a.m. |
| PD | Predicate disambiguation | batch_69fd4fd1a58881909d4b84de1b24e380 |
completed | May 8, 2026, 2:52 a.m. |
Created at: May 1, 2026, 1:26 a.m.