Triple
T13569528
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spellmonger series |
E324120
|
entity |
| Predicate | readerCommunity |
P9917
|
FINISHED |
| Object | strong online fanbase |
—
|
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: strong online fanbase | Statement: [Spellmonger series, readerCommunity, strong online fanbase]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: readerCommunity Context triple: [Spellmonger series, readerCommunity, strong online fanbase]
-
A.
readership
chosen
Indicates the relationship in which one party reads, follows, or is the audience for the written or published work of another.
-
B.
readerReception
Indicates how readers interpret, respond to, or are affected by a particular text or work.
-
C.
reading
Indicates that an entity is engaged in the activity of interpreting and understanding written or printed material from another entity or source.
-
D.
readingOrganizer
Indicates that an entity is responsible for planning, managing, or coordinating reading-related activities or materials for others.
-
E.
readingAid
Indicates that one entity assists or facilitates another entity’s ability to read or engage in reading activities.
- 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_69d8076830b48190910a902bae5888e2 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbb00f5b8881908617f42d227ed137 |
completed | April 12, 2026, 2:45 p.m. |
| PD | Predicate disambiguation | batch_69dbae161a0481909f9d3f40ca4e0ac5 |
completed | April 12, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:48 p.m.