Triple
T10286494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ozian |
E241240
|
entity |
| Predicate | usedInFandom |
P40776
|
FINISHED |
| Object | Oz fandom |
—
|
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: Oz fandom | Statement: [Ozian, usedInFandom, Oz fandom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInFandom Context triple: [Ozian, usedInFandom, Oz fandom]
-
A.
fandomContext
chosen
Indicates that the relationship or action occurs specifically within the context of a particular fandom or fan community.
-
B.
fandomCulture
Indicates a relationship where one entity is associated with, shaped by, or participates in the shared practices, norms, and creative activities of a particular fan community.
-
C.
fandomInterpretation
Indicates a relationship where an entity represents or expresses a fan-created interpretation, theory, or reading of another work or element within a fandom.
-
D.
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.
-
E.
fandomType
Indicates the specific category or kind of fandom relationship that exists between an entity and the subject of that fandom.
- 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_69d381aaafc08190af475ef58dc16aba |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d7ccb7ec8190a538cf279e48116e |
completed | April 7, 2026, 10:09 a.m. |
| PD | Predicate disambiguation | batch_69d4d1f117708190928f92ae2611d724 |
completed | April 7, 2026, 9:44 a.m. |
Created at: April 6, 2026, 11:40 a.m.