Triple
T29723446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AO3 |
E752118
|
entity |
| Predicate | supportsFandoms |
P191982
|
FINISHED |
| Object | multiple fandoms |
—
|
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: multiple fandoms | Statement: [AO3, supportsFandoms, multiple fandoms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsFandoms Context triple: [AO3, supportsFandoms, multiple fandoms]
-
A.
hasFandomAssociation
chosen
Indicates a relationship where an entity is associated with, connected to, or recognized within a particular fandom or fan community.
-
B.
hasFandomElement
Indicates that something includes, features, or is associated with an element derived from or related to a fandom.
-
C.
fandomSharedWith
Indicates that two or more entities share interest or participation in the same fandom.
-
D.
fandomBase
Indicates that one entity serves as the primary fan community, origin, or core support base for another entity.
-
E.
fandomElement
Indicates a relationship where something is a notable component, motif, or feature within a particular fandom or fan community.
- 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_69f0d628c00c8190ab5ee7e423d7ec3c |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e0f3d88190a4ee7b0673f1ef90 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 28, 2026, 7:37 p.m.