Triple
T28197332
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jenny Frost |
E716480
|
entity |
| Predicate | replacedMemberOfAtomicKitten |
P124194
|
FINISHED |
| Object | Kerry Katona |
—
|
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: Kerry Katona | Statement: [Jenny Frost, replacedMemberOfAtomicKitten, Kerry Katona]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacedMemberOfAtomicKitten Context triple: [Jenny Frost, replacedMemberOfAtomicKitten, Kerry Katona]
-
A.
formerMemberOf
Indicates that an entity once belonged to or was affiliated with a group, organization, or body, but is no longer a member.
-
B.
hasMemberWhoBecame
Indicates that a group or organization includes at least one member who later attained or transitioned into a specified role, status, or affiliation.
-
C.
replacementMember
Indicates that one entity serves as a substitute or successor taking over the role, position, or function previously held by another entity.
-
D.
replacedInLineupBy
chosen
Indicates that one participant in a lineup is substituted or superseded by another participant in that same lineup.
-
E.
memberFrom
Indicates that an entity is a member originating from, or associated with, a particular source, group, or location.
- 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_69efd6b612f48190a72012b520afbd10 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f71996e1a48190ac59a1d66d7c44e8 |
completed | May 3, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69f71820c6c88190ab38b4fa626d22cc |
completed | May 3, 2026, 9:40 a.m. |
Created at: April 27, 2026, 10:28 p.m.