Triple
T30599812
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Óin |
E778874
|
entity |
| Predicate | speciesInFandom |
P125185
|
FINISHED |
| Object | Dwarf (Tolkien legendarium) |
—
|
NE NERFINISHED |
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: Dwarf (Tolkien legendarium) | Statement: [Óin, speciesInFandom, Dwarf (Tolkien legendarium)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: speciesInFandom Context triple: [Óin, speciesInFandom, Dwarf (Tolkien legendarium)]
-
A.
fandomType
Indicates the specific category or kind of fandom relationship that exists between an entity and the subject of that fandom.
-
B.
subjectOfFandom
Indicates that one entity is the focus or object of another entity’s fandom, admiration, or devoted interest.
-
C.
fandomScope
Indicates the extent or boundaries of a fandom-related relationship, such as how broadly or narrowly a fan’s interest, participation, or recognition applies.
-
D.
fandomCharacteristic
Indicates that an entity possesses a particular trait, behavior, or quality specifically in the context of its fandom or fan community.
-
E.
fandomClassification
chosen
Indicates how an entity is categorized or grouped 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_69f224a1570c8190a85d3ac330479a79 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f73223675481908c1bc3208c0f5284 |
completed | May 3, 2026, 11:31 a.m. |
| PD | Predicate disambiguation | batch_69f7317690108190b3aae2cd2e1d069e |
completed | May 3, 2026, 11:28 a.m. |
Created at: April 29, 2026, 8:25 p.m.