Triple
T24644525
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rhea Ripley |
E610067
|
entity |
| Predicate | firstHolderOf |
P153898
|
FINISHED |
| Object | NXT UK Women’s Championship |
—
|
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: NXT UK Women’s Championship | Statement: [Rhea Ripley, firstHolderOf, NXT UK Women’s Championship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstHolderOf Context triple: [Rhea Ripley, firstHolderOf, NXT UK Women’s Championship]
-
A.
first_holder
chosen
Indicates that the subject is the earliest or original holder or possessor of the specified object, title, or right.
-
B.
firstHolderInCanon
Indicates that the subject is the earliest entity, in the canonical timeline or storyline, known to have held or possessed the specified object, title, or role.
-
C.
firstHeldAs
Indicates the initial time or context in which an entity was first possessed, owned, or held by another entity.
-
D.
firstModernHolder
Indicates that the subject is the earliest or original modern entity to hold or possess the specified object, title, or role.
-
E.
wasFirstHeldBy
Indicates that an event or activity was initially hosted, organized, or conducted by a particular entity.
- F. None of above.
Provenance (3 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. |
Created at: April 18, 2026, 2:33 a.m.