Triple
T22578421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | She’s My Hero |
E544487
|
entity |
| Predicate | hasFandomElement |
P148800
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [She’s My Hero, hasFandomElement, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFandomElement Context triple: [She’s My Hero, hasFandomElement, yes]
-
A.
hasFandomDesignation
Indicates that an entity has a specific name or label used by its fan community to refer to it or its fandom.
-
B.
hasFandomWithinStory
Indicates that within the narrative of a story, one entity is a fan or admirer of another entity (such as a character, group, or work) that exists inside that same story world.
-
C.
fandomType
Indicates the specific category or kind of fandom relationship that exists between an entity and the subject of that fandom.
-
D.
fandomUses
Indicates that a fandom makes use of, relies on, or incorporates a particular resource, tool, platform, or element.
-
E.
fandomSharedWith
Indicates that two or more entities share interest or participation in the same fandom.
- F. None of above. chosen
Provenance (4 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_69e11e30d05481909df915354c89f0d6 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f15feee27c8190b31c923e1f00a363 |
completed | April 29, 2026, 1:33 a.m. |
| PD | Predicate disambiguation | batch_69ee626e6bb08190ada4dd8b48cc0c43 |
completed | April 26, 2026, 7:07 p.m. |
| PDg | Predicate description generation | batch_69ee8841e9cc81908d23b34215e3be71 |
completed | April 26, 2026, 9:48 p.m. |
Created at: April 16, 2026, 8:53 p.m.