Triple
T37573278
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AlDub |
E934744
|
entity |
| Predicate | roseToFameThrough |
P171669
|
FINISHED |
| Object | Kalyeserye |
—
|
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: Kalyeserye | Statement: [AlDub, roseToFameThrough, Kalyeserye]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roseToFameThrough Context triple: [AlDub, roseToFameThrough, Kalyeserye]
-
A.
achievedPopularityVia
chosen
Indicates that an entity gained recognition or widespread acceptance through a particular method, channel, or means.
-
B.
basedOnFameFrom
Indicates that something is determined, influenced, or derived from the level or source of fame associated with an entity.
-
C.
starMadeFamous
Indicates that one entity (such as a work, event, or role) is what caused another entity (typically a person) to become widely known or famous.
-
D.
gainedProminenceAs
Indicates that an entity became widely recognized or notable in the role, capacity, or identity specified by another entity.
-
E.
fameFor
Indicates that one entity is widely known or recognized specifically because of, or in connection with, 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_69f76ecd99148190be327e391a70f5b6 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba61dff5081909fec88a7aeb0c8a1 |
completed | May 6, 2026, 8:35 p.m. |
| PD | Predicate disambiguation | batch_69fba350e9a8819095893229d9643572 |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.