Triple
T15122661
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beliebers |
E361205
|
entity |
| Predicate | relatedFandom |
P110750
|
FINISHED |
| Object | Arianators |
—
|
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: Arianators | Statement: [Beliebers, relatedFandom, Arianators]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedFandom Context triple: [Beliebers, relatedFandom, Arianators]
-
A.
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.
-
B.
fandomType
Indicates the specific category or kind of fandom relationship that exists between an entity and the subject of that fandom.
-
C.
fandomFocus
Indicates that one entity is primarily centered on, dedicated to, or concerned with the fan community or fan-related aspects of another entity.
-
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.
fandomSharedWith
chosen
Indicates that two or more entities share interest or participation in the same 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_69d85a06450081909c5a14ea9851a15e |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0059f69a881909929a037a0eef702 |
completed | April 15, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69deb96c1d9c81909351558ed97bc5b7 |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:06 a.m.