Triple
T27949610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BTS |
E703385
|
entity |
| Predicate | socialMediaFollowerCountCategory |
P73542
|
FINISHED |
| Object | hundreds of millions |
—
|
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: hundreds of millions | Statement: [BTS, socialMediaFollowerCountCategory, hundreds of millions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: socialMediaFollowerCountCategory Context triple: [BTS, socialMediaFollowerCountCategory, hundreds of millions]
-
A.
socialMediaFollowerCount
chosen
Indicates the number of followers an entity has on a social media platform.
-
B.
socialMediaCategory
Indicates the classification or type of social media context, platform, or content associated with an entity or interaction.
-
C.
socialMediaPlatformAssociatedWith
Indicates that there is an association or linkage between an entity and a specific social media platform.
-
D.
socialSphereFocus
Indicates a focus of attention, activity, or influence directed toward a particular social group or sphere of relationships.
-
E.
socialType
Indicates the category or nature of a social relationship or interaction that exists between entities.
- 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_69ef840c8b2c8190946ae9522774ba51 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f68805b4848190b75da14996d52a38 |
completed | May 2, 2026, 11:25 p.m. |
| PD | Predicate disambiguation | batch_69f68609c0b08190a8e1238a4d97c270 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 27, 2026, 7:24 p.m.