Triple
T23731672
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | S.Coups |
E586423
|
entity |
| Predicate | fandomNameAssociation |
P153741
|
FINISHED |
| Object | Carat (Seventeen fandom) |
—
|
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: Carat (Seventeen fandom) | Statement: [S.Coups, fandomNameAssociation, Carat (Seventeen fandom)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fandomNameAssociation Context triple: [S.Coups, fandomNameAssociation, Carat (Seventeen fandom)]
-
A.
fandomType
Indicates the specific category or kind of fandom relationship that exists between an entity and the subject of that fandom.
-
B.
fandomBase
Indicates that one entity serves as the primary fan community, origin, or core support base for another entity.
-
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.
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. 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_69e24907dc9c8190be074c9c96a0ec2d |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1baccf5b88190961a6e5e0e1407c7 |
completed | April 29, 2026, 8:01 a.m. |
| PD | Predicate disambiguation | batch_69f155e4b1148190836ede4741dcb888 |
completed | April 29, 2026, 12:50 a.m. |
| PDg | Predicate description generation | batch_69f15b453da88190889a8d9b21727958 |
completed | April 29, 2026, 1:13 a.m. |
Created at: April 17, 2026, 7:09 p.m.