Triple
T37573286
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AlDub |
E934744
|
entity |
| Predicate | fandomDrivenBy |
P188729
|
FINISHED |
| Object | social media |
—
|
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: social media | Statement: [AlDub, fandomDrivenBy, social media]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fandomDrivenBy Context triple: [AlDub, fandomDrivenBy, social media]
-
A.
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.
-
B.
fandomFocus
Indicates that one entity is primarily centered on, dedicated to, or concerned with the fan community or fan-related aspects of another entity.
-
C.
fandomType
Indicates the specific category or kind of fandom relationship that exists between an entity and the subject of that fandom.
-
D.
fandomCulture
Indicates a relationship where one entity is associated with, shaped by, or participates in the shared practices, norms, and creative activities of a particular fan community.
-
E.
fandomActivity
Indicates participation in or engagement with fan-related activities centered around a particular work, person, or franchise.
- 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_69f76ecd99148190be327e391a70f5b6 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbacaf54648190811ea33b34907e8e |
completed | May 6, 2026, 9:03 p.m. |
| PD | Predicate disambiguation | batch_69fba883f770819091059c6f6c6af9f7 |
completed | May 6, 2026, 8:45 p.m. |
| PDg | Predicate description generation | batch_69fbacaea12c8190a4c99e64335f0e7e |
completed | May 6, 2026, 9:03 p.m. |
Created at: May 3, 2026, 4:17 p.m.