Triple
T37573307
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AlDub |
E934744
|
entity |
| Predicate | notableHashtag |
P9354
|
FINISHED |
| Object | #ALDUBEBTamangPanahon |
—
|
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: #ALDUBEBTamangPanahon | Statement: [AlDub, notableHashtag, #ALDUBEBTamangPanahon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableHashtag Context triple: [AlDub, notableHashtag, #ALDUBEBTamangPanahon]
-
A.
hashtag
chosen
Indicates that an entity is associated with or labeled by a specific hashtag, typically used for categorization or topic tagging.
-
B.
usedInHashtag
Indicates that something (such as a word, phrase, or entity) is employed as part of a hashtag.
-
C.
socialPhenomenon
Indicates a relationship where an event, behavior, or pattern emerges from and affects interactions within a society or group.
-
D.
notableDuring
Indicates that something was especially prominent, active, or significant during a particular time period or event.
-
E.
notableHub
Indicates that an entity serves as a significant central point or focal location for activities, connections, or influence within a particular context.
- 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_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a1553e08190bb7424c448cb1f33 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:17 p.m.