Triple
T35806608
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Texas Red |
E1035116
|
entity |
| Predicate | wrestlerRealName |
P186413
|
FINISHED |
| Object | Mark William Calaway |
—
|
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: Mark William Calaway | Statement: [Texas Red, wrestlerRealName, Mark William Calaway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wrestlerRealName Context triple: [Texas Red, wrestlerRealName, Mark William Calaway]
-
A.
nicknameOfAssociatedWrestler
Indicates that one entity is a nickname that is used to refer to an associated professional wrestler.
-
B.
wrestlingRingName
Indicates the designated name or title assigned to a specific wrestling ring.
-
C.
developedWrestler
Indicates that one entity (such as a trainer, organization, or promotion) played a significant role in training, shaping, or advancing the professional wrestling career of another entity (the wrestler).
-
D.
trainedWrestlersOn
Indicates that one entity has trained wrestlers on or for another entity, such as a team, organization, or event.
-
E.
pinnedWrestler
Indicates that one wrestler has held another wrestler's shoulders to the mat in a position that could result in a pin or fall.
- F. None of above. chosen
Provenance (4 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_69f7cec454a88190a9f3bbee2b856636 |
completed | May 3, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69f7c8977c288190997a892ec5f756ed |
completed | May 3, 2026, 10:13 p.m. |
| PDg | Predicate description generation | batch_69f7cec398ac819081c954a993c323ee |
completed | May 3, 2026, 10:40 p.m. |
Created at: May 3, 2026, 4:06 p.m.