Triple
T36778822
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | G.R.L. |
E908711
|
entity |
| Predicate | hasFanbaseType |
P197185
|
FINISHED |
| Object | pop music fans |
—
|
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: pop music fans | Statement: [G.R.L., hasFanbaseType, pop music fans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFanbaseType Context triple: [G.R.L., hasFanbaseType, pop music fans]
-
A.
hasFanBaseFrom
Indicates that an entity has a significant group of supporters or followers originating from a specified place, group, or source.
-
B.
hasFanBaseFor
Indicates that an entity has a group of supporters or admirers specifically dedicated to another entity (such as a work, person, or brand).
-
C.
hasFanBaseDepictedAs
Indicates that an entity has a fan base that is visually or narratively represented in some form (e.g., in media, artwork, or documentation).
-
D.
hasFanBaseTension
Indicates a relationship where there is conflict, rivalry, or strained relations between the fan bases of the related entities.
-
E.
hasGlobalFanBase
Indicates that an entity is widely recognized and followed by fans across multiple countries or regions.
- 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_69f76e798aa08190ace31098d1b13e9f |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fe7b1c506c8190869c1a22031e0571 |
completed | May 9, 2026, 12:09 a.m. |
| PD | Predicate disambiguation | batch_69fe796b2bdc8190a86980d44008f875 |
completed | May 9, 2026, 12:01 a.m. |
| PDg | Predicate description generation | batch_69fe7b1b3460819081172731b52ac15b |
completed | May 9, 2026, 12:08 a.m. |
Created at: May 3, 2026, 4:12 p.m.