Triple
T30345543
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Type-Moon |
E771858
|
entity |
| Predicate | fanCommunity |
P48181
|
FINISHED |
| Object | active dōjin culture |
—
|
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: active dōjin culture | Statement: [Type-Moon, fanCommunity, active dōjin culture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fanCommunity Context triple: [Type-Moon, fanCommunity, active dōjin culture]
-
A.
fanAccess
Indicates that an entity has permission or the ability to access fan-related content, features, or areas associated with another entity.
-
B.
hasFanCommunity
chosen
Indicates that an entity is associated with a group of fans who actively follow, support, or engage around it.
-
C.
fanOwned
Indicates that the entity is owned or controlled by fans, typically through collective or community-based ownership rather than traditional private or corporate ownership.
-
D.
fandomCommunity
Indicates a relationship where individuals are connected through shared enthusiasm and participation in a fan community centered around a particular work, person, or interest.
-
E.
fanDiscussion
Indicates a discussion or conversation among fans about a shared interest, such as a work, person, or event they follow.
- 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_69f2248b9a208190bc3e6804acd5afd6 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f682073b00819087f197f3937071a5 |
completed | May 2, 2026, 11 p.m. |
| PD | Predicate disambiguation | batch_69f67603526c81908295a1ece8727c66 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 29, 2026, 7:55 p.m.