Triple
T23594693
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harmonizers |
E582579
|
entity |
| Predicate | fandomOfGroupFormedOn |
P152849
|
FINISHED |
| Object | The X Factor USA |
—
|
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: The X Factor USA | Statement: [Harmonizers, fandomOfGroupFormedOn, The X Factor USA]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fandomOfGroupFormedOn Context triple: [Harmonizers, fandomOfGroupFormedOn, The X Factor USA]
-
A.
fandomSharedWith
Indicates that two or more entities share interest or participation in the same fandom.
-
B.
fandomType
Indicates the specific category or kind of fandom relationship that exists between an entity and the subject of that fandom.
-
C.
fandomActivity
Indicates participation in or engagement with fan-related activities centered around a particular work, person, or franchise.
-
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.
fandomUses
Indicates that a fandom makes use of, relies on, or incorporates a particular resource, tool, platform, or element.
- 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_69e248f9e0a08190814772847003b1ff |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b08e9aa4819091099dfc2074b22d |
completed | April 29, 2026, 7:17 a.m. |
| PD | Predicate disambiguation | batch_69f118c96a0081908a8ac98ef7e7e60c |
completed | April 28, 2026, 8:30 p.m. |
| PDg | Predicate description generation | batch_69f121cc494081908c987adfcde89b0e |
completed | April 28, 2026, 9:08 p.m. |
Created at: April 17, 2026, 6:42 p.m.