Triple
T37573305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AlDub |
E934744
|
entity |
| Predicate | TamangPanahonPurpose |
P189068
|
FINISHED |
| Object | charity event for libraries |
—
|
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: charity event for libraries | Statement: [AlDub, TamangPanahonPurpose, charity event for libraries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: TamangPanahonPurpose Context triple: [AlDub, TamangPanahonPurpose, charity event for libraries]
-
A.
Tamang PanahonHeldAt
Indicates that the event "Tamang Panahon" was held or took place at a specific location or venue.
-
B.
TamangPanahonYear
Indicates a temporal relationship specifying that something occurs in, is associated with, or is valid for a particular year referred to as the “Tamang Panahon” year.
-
C.
תקופה עלילתית
Indicates a narrative relationship where a specific time period serves as the setting or temporal framework for the plot or events of a story.
-
D.
culturalPeriod
Indicates the historical or cultural era with which an entity is associated or during which it was created, used, or significant.
-
E.
timeExistence
Indicates the period or duration during which an entity exists or is valid.
- 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_69fbb084760c8190a1554985d3c3cb7a |
completed | May 6, 2026, 9:20 p.m. |
| PD | Predicate disambiguation | batch_69fbadf3cb548190ba3b7514f76b790a |
completed | May 6, 2026, 9:09 p.m. |
| PDg | Predicate description generation | batch_69fbb083ab708190a18b045311106f27 |
completed | May 6, 2026, 9:20 p.m. |
Created at: May 3, 2026, 4:17 p.m.