Triple
T27208811
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maine Mendoza |
E683943
|
entity |
| Predicate | partnerInLoveTeam |
P165070
|
FINISHED |
| Object | Alden Richards |
—
|
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: Alden Richards | Statement: [Maine Mendoza, partnerInLoveTeam, Alden Richards]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partnerInLoveTeam Context triple: [Maine Mendoza, partnerInLoveTeam, Alden Richards]
-
A.
partnerInMyth
Indicates a mythological relationship in which two entities are partners or companions within the same myth or mythic narrative.
-
B.
spouseOfTeam
Indicates that one entity is the spouse of a member of the specified team.
-
C.
partnerInBattle
Indicates that two entities are allied or cooperate as partners in the same battle or combat engagement.
-
D.
partnerInMission
Indicates that two or more entities collaborate as partners in carrying out the same mission or operation.
-
E.
partnerInSeries
Indicates that two entities are co-participants or collaborators within the same series, jointly contributing to or appearing in that ongoing sequence.
- 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_69eefad339a08190aeacb2a198f1a39b |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f65705a3048190a3728b695ba2ae65 |
completed | May 2, 2026, 7:56 p.m. |
| PD | Predicate disambiguation | batch_69f651a931748190a637e631a52bbfaa |
completed | May 2, 2026, 7:34 p.m. |
| PDg | Predicate description generation | batch_69f6562ef4e4819082ce6abd41b74dc5 |
completed | May 2, 2026, 7:53 p.m. |
Created at: April 27, 2026, 9:38 a.m.