Triple
T24644533
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rhea Ripley |
E610067
|
entity |
| Predicate | stablePartner |
P156888
|
FINISHED |
| Object | Finn Bálor |
—
|
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: Finn Bálor | Statement: [Rhea Ripley, stablePartner, Finn Bálor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stablePartner Context triple: [Rhea Ripley, stablePartner, Finn Bálor]
-
A.
coalitionStability
Indicates the degree to which a coalition is likely to remain intact without members defecting or the alliance breaking apart.
-
B.
starPairing
Indicates a relationship where two stars are associated or grouped together as a pair, typically for observational, analytical, or classificatory purposes.
-
C.
matchmaker
Indicates that one entity facilitates or arranges a romantic or marital relationship between two other entities.
-
D.
pairsIntroduced
Indicates that one entity has brought together or facilitated the first meeting between two other entities as a pair.
-
E.
isPerfectPairing
Indicates that two entities complement each other exceptionally well, forming an ideal or highly compatible combination.
- 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_69e2c4d350a481909170482bc2ce6af9 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f41011d8048190be70329ba0bfb7c7 |
completed | May 1, 2026, 2:29 a.m. |
| PD | Predicate disambiguation | batch_69f40ed9d47881909fcfc0d04e8d074a |
completed | May 1, 2026, 2:24 a.m. |
| PDg | Predicate description generation | batch_69f41010f06c81908ee7f773220df14f |
completed | May 1, 2026, 2:29 a.m. |
Created at: April 18, 2026, 2:33 a.m.