Triple
T35628333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bayley and Sasha Banks |
E1029516
|
entity |
| Predicate | memberRealName |
P9233
|
FINISHED |
| Object | Pamela Rose Martinez (Bayley) |
—
|
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: Pamela Rose Martinez (Bayley) | Statement: [Bayley and Sasha Banks, memberRealName, Pamela Rose Martinez (Bayley)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: memberRealName Context triple: [Bayley and Sasha Banks, memberRealName, Pamela Rose Martinez (Bayley)]
-
A.
realName
chosen
Indicates that one entity is the actual, full, or birth name of another entity, which may be known by an alias, nickname, or alternate identity.
-
B.
usedByRealName
Indicates that something (such as an alias, handle, or resource) is used by an entity identified by their real, legal name.
-
C.
fullNameRevealed
Indicates that an entity’s complete personal name has been disclosed or made known to another party or in a given context.
-
D.
member2CurrentName
Indicates that the second member entity is associated with its current (most recent or active) name.
-
E.
member3CurrentName
Indicates that an entity’s currently used name is the third in a sequence of its known or recorded names.
- 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_69f76e07bb0c8190968ea2d836fc42c9 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd5bf69acc819092a01e4259785dc3 |
completed | May 8, 2026, 3:43 a.m. |
| PD | Predicate disambiguation | batch_69fd59b3f4ac8190a7f9dd3142da6e09 |
completed | May 8, 2026, 3:34 a.m. |
Created at: May 3, 2026, 4:05 p.m.