Triple
T35807121
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boneyard Match |
E1035129
|
entity |
| Predicate | matchTypeDebut |
P184195
|
FINISHED |
| Object | The Undertaker vs AJ Styles |
—
|
LITERAL 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 vs AJ Styles | Statement: [Boneyard Match, matchTypeDebut, The Undertaker vs AJ Styles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: matchTypeDebut Context triple: [Boneyard Match, matchTypeDebut, The Undertaker vs AJ Styles]
-
A.
matchType
Indicates the specific category or nature of how two or more entities correspond or align with each other within a given context.
-
B.
matchOf
Indicates that one entity is a specific match, counterpart, or corresponding instance of another entity within a defined context or set.
-
C.
featuredMatchType
Indicates the specific category or kind of match that is highlighted or given special prominence.
-
D.
matchTypes
Indicates that two or more entities share the same type or category according to a specified classification.
-
E.
matchesType
Indicates that one entity has the same or a compatible type as another entity according to a defined type system or classification.
- 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_69f7acaec1508190a38f2ac9cc5383e7 |
completed | May 3, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69f7ab734d848190a84f9b8c3a952b75 |
completed | May 3, 2026, 8:09 p.m. |
| PDg | Predicate description generation | batch_69f7ac2210e481909279dade5328825c |
completed | May 3, 2026, 8:12 p.m. |
Created at: May 3, 2026, 4:06 p.m.