Triple
T37573246
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kalyeserye |
E934743
|
entity |
| Predicate | hasCouple |
P152718
|
FINISHED |
| Object | Alden Richards and Maine Mendoza |
E936897
|
NE 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: Alden Richards and Maine Mendoza | Statement: [Kalyeserye, hasCouple, Alden Richards and Maine Mendoza]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCouple Context triple: [Kalyeserye, hasCouple, Alden Richards and Maine Mendoza]
-
A.
hasMainCouple
chosen
Indicates that a work or narrative features a primary romantic couple who are the central focus of its relationship storyline.
-
B.
marriedCouple
Indicates that two individuals are legally and/or socially recognized as being married to each other as a couple.
-
C.
couplesTo
Indicates that one entity is joined or linked to another in a way that allows interaction, transfer, or mutual influence between them.
-
D.
isMarriedToA
Indicates that one entity is legally and socially bound in marriage to another specific entity.
-
E.
hasExPartner
Indicates that one entity was formerly in a romantic or intimate partnership with another entity, but that relationship has ended.
- F. None of above.
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_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a409f2093608190ab6a6e4ffdcdb9f9 |
completed | June 28, 2026, 4:12 a.m. |
| PD | Predicate disambiguation | batch_6a037a1553e08190bb7424c448cb1f33 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:17 p.m.