Triple
T35806551
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Calaway |
E1035114
|
entity |
| Predicate | hasNotableStageNameDerivedFromBearer |
P206059
|
FINISHED |
| Object | The Undertaker |
E318019
|
NE FINISHED |
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 Undertaker | Statement: [Calaway, hasNotableStageNameDerivedFromBearer, The Undertaker]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableStageNameDerivedFromBearer Context triple: [Calaway, hasNotableStageNameDerivedFromBearer, The Undertaker]
-
A.
hasGivenNameOfBearer
Indicates that a bearer (such as a person or entity) has a specific given (first) name.
-
B.
usedAsStageNameBySomeBearers
Indicates that the name is employed as a stage name by at least some of its bearers.
-
C.
bearerStageName
Indicates that an entity is known or performs under a particular stage name.
-
D.
hasNotableBearerSurname
Indicates that a surname is associated with at least one notable or well-known individual who bears it.
-
E.
hasNameBearerRole
Indicates that an entity holds or fulfills the role of bearing or carrying a particular name.
- F. None of above. chosen
Provenance (5 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_6a037ce70f54819082946dad8d380825 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a397d64825481909323a3599f552dd4 |
completed | June 22, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_6a037a069e6c8190857b611fffb7b867 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037ce53de881908cf14141cf3bc570 |
completed | May 12, 2026, 7:17 p.m. |
Created at: May 3, 2026, 4:06 p.m.