Triple
T37573234
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kalyeserye |
E934743
|
entity |
| Predicate | hasMainCast |
P132280
|
FINISHED |
| Object | Maine Mendoza |
E683943
|
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: Maine Mendoza | Statement: [Kalyeserye, hasMainCast, Maine Mendoza]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainCast Context triple: [Kalyeserye, hasMainCast, Maine Mendoza]
-
A.
hasMainStars
Indicates that an entity (such as a film, show, or performance) features the specified entities as its principal or leading performers.
-
B.
hasHumanCast
Indicates that a work or production features human performers as part of its cast.
-
C.
hasMainCastSize
Indicates the relationship that specifies the number of principal or main cast members associated with an entity.
-
D.
mainCastIncludes
chosen
Indicates that a work’s primary cast features the specified person or character as one of its main members.
-
E.
hasMainRole
Indicates that an entity holds the primary or most significant role in relation to another entity or context.
- 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_6a40a7f1b98881908bda610d39b493ed |
completed | June 28, 2026, 4:49 a.m. |
| PD | Predicate disambiguation | batch_6a037a1553e08190bb7424c448cb1f33 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:17 p.m.