Triple
T35808156
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mercedes KV |
E1035155
|
entity |
| Predicate | hasAlternativeRingName |
P87629
|
FINISHED |
| Object | Sasha Banks |
—
|
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: Sasha Banks | Statement: [Mercedes KV, hasAlternativeRingName, Sasha Banks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAlternativeRingName Context triple: [Mercedes KV, hasAlternativeRingName, Sasha Banks]
-
A.
hasRingName
chosen
Indicates that an entity is associated with, or designated by, a specific ring name.
-
B.
hasAlternativeFamilyName
Indicates that an entity is associated with an additional or variant family name besides its primary family name.
-
C.
hasAlternativeNamesakeRole
Indicates that an entity serves in an additional or alternative role as a namesake, distinct from its primary namesake role.
-
D.
hasAlternativeNameForSameCity
Indicates that one city name is an alternative or variant name referring to the same city as another name.
-
E.
hasAlternativeNameInYorkRegion
Indicates that an entity is known by an alternative name specifically within the York Region jurisdiction.
- 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_69f76e1762408190b885a8456862e372 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fdd5fba5048190b7d430ae2054a1fd |
completed | May 8, 2026, 12:24 p.m. |
| PD | Predicate disambiguation | batch_69fdd35f76f88190a1854ea27132f9c7 |
completed | May 8, 2026, 12:13 p.m. |
Created at: May 3, 2026, 4:06 p.m.