Triple
T35208026
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Becky Lynch |
E1016592
|
entity |
| Predicate | signatureNickname |
P119158
|
FINISHED |
| Object | The Man |
—
|
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: The Man | Statement: [Becky Lynch, signatureNickname, The Man]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signatureNickname Context triple: [Becky Lynch, signatureNickname, The Man]
-
A.
signatureStyle
Indicates the characteristic way in which an entity typically signs its name or marks documents, distinguishing its unique signing pattern or format.
-
B.
signatureStyleOf
Indicates that something represents the characteristic or distinctive signature style associated with a particular entity.
-
C.
signature
Indicates that one entity has provided an official or personal signed endorsement, authorization, or acknowledgment on or for another entity.
-
D.
signaturePersona
chosen
Indicates that an entity serves as the primary or defining persona, identity, or character most closely associated with another entity.
-
E.
signatureSubject
Indicates that an entity serves as the subject or principal party associated with a given signature.
- 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_69f76ddf549c8190869d0af076fd2c28 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78f63c8788190b253a18de5ca1312 |
completed | May 3, 2026, 6:09 p.m. |
| PD | Predicate disambiguation | batch_69f78e2d71248190b850c2802ec170c0 |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4:02 p.m.