Triple
T23995134
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WWE tag team division |
E605167
|
entity |
| Predicate | featuredOnEvent |
P997
|
FINISHED |
| Object | WrestleMania |
—
|
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: WrestleMania | Statement: [WWE tag team division, featuredOnEvent, WrestleMania]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuredOnEvent Context triple: [WWE tag team division, featuredOnEvent, WrestleMania]
-
A.
featuredOn
chosen
Indicates that one entity is prominently presented, highlighted, or showcased on or within another entity (such as a platform, publication, or product).
-
B.
featuresEvent
Indicates that an entity includes, presents, or highlights a particular event as part of its content or offering.
-
C.
featuredIn
Indicates that one entity appears or is prominently included within another entity, such as a person, work, or item being showcased in a larger work, event, or context.
-
D.
featuredFor
Indicates that one entity is highlighted, promoted, or specially showcased in the context or for the benefit of another entity.
-
E.
featuredBout
Indicates that a particular bout or match is highlighted or given special prominence within a card, event, or collection of bouts.
- 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_69e295463f7c8190b1c19dbd114641b9 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1d38ec7cc8190b91cfa09f88dacc6 |
completed | April 29, 2026, 9:46 a.m. |
| PD | Predicate disambiguation | batch_69f1615994c48190a5de95d3f7e5cd0a |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 9:38 p.m.