Triple
T23594685
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harmonizers |
E582579
|
entity |
| Predicate | fandomNameOf |
P23575
|
FINISHED |
| Object | Fifth Harmony |
—
|
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: Fifth Harmony | Statement: [Harmonizers, fandomNameOf, Fifth Harmony]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fandomNameOf Context triple: [Harmonizers, fandomNameOf, Fifth Harmony]
-
A.
fandomNickname
chosen
Indicates that one entity is the nickname used by fans to refer to another entity (such as a person, group, or work).
-
B.
fandomType
Indicates the specific category or kind of fandom relationship that exists between an entity and the subject of that fandom.
-
C.
fandomBase
Indicates that one entity serves as the primary fan community, origin, or core support base for another entity.
-
D.
fandomIdentity
Indicates that an entity identifies as a fan or member of a particular fandom associated with another entity.
-
E.
fandomFocus
Indicates that one entity is primarily centered on, dedicated to, or concerned with the fan community or fan-related aspects of another entity.
- 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_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. |
Created at: April 17, 2026, 6:42 p.m.