Triple
T21252087
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Web-Head |
E523768
|
entity |
| Predicate | hasFandomUsage |
P139340
|
FINISHED |
| Object | Spider-Man fans |
—
|
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: Spider-Man fans | Statement: [Web-Head, hasFandomUsage, Spider-Man fans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFandomUsage Context triple: [Web-Head, hasFandomUsage, Spider-Man fans]
-
A.
fandomUses
chosen
Indicates that a fandom makes use of, relies on, or incorporates a particular resource, tool, platform, or element.
-
B.
hasFandomDesignation
Indicates that an entity has a specific name or label used by its fan community to refer to it or its fandom.
-
C.
hasPopularUse
Indicates that something is widely used, accepted, or favored by a large number of people or within a broad context.
-
D.
fandomSignificance
Indicates the degree to which something holds importance, influence, or prominence within a particular fan community or fandom context.
-
E.
hasFanCommunity
Indicates that an entity is associated with a group of fans who actively follow, support, or engage around it.
- 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_69e0b5146c108190adc9adb73e90abff |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7359e90d881909b3153f1e7213c5c |
completed | April 21, 2026, 8:30 a.m. |
| PD | Predicate disambiguation | batch_69e5f61239708190ab7b3c83ae848a0d |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 3:57 p.m.