Triple
T29222869
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grobanites |
E740847
|
entity |
| Predicate | fandomGenre |
P166439
|
FINISHED |
| Object | classical crossover |
—
|
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: classical crossover | Statement: [Grobanites, fandomGenre, classical crossover]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fandomGenre Context triple: [Grobanites, fandomGenre, classical crossover]
-
A.
fandomType
Indicates the specific category or kind of fandom relationship that exists between an entity and the subject of that fandom.
-
B.
fandomClassification
Indicates how an entity is categorized or grouped within a particular fandom or fan community.
-
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.
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.
-
E.
subjectOfFandom
Indicates that one entity is the focus or object of another entity’s fandom, admiration, or devoted interest.
- F. None of above. chosen
Provenance (4 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_69f07cbb12bc81908c1971d9de9a8d2a |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f664340df481909c9b6ba0d0403120 |
completed | May 2, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f65c24f8b48190af81b575f3c15be5 |
completed | May 2, 2026, 8:18 p.m. |
| PDg | Predicate description generation | batch_69f65fb2ead08190b06677d4d6ea1ea8 |
completed | May 2, 2026, 8:33 p.m. |
Created at: April 28, 2026, 12:16 p.m.