Triple
T35493168
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WWF Attitude Era |
E1025783
|
entity |
| Predicate | mainRivalPromotion |
P183352
|
FINISHED |
| Object | World Championship Wrestling |
—
|
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: World Championship Wrestling | Statement: [WWF Attitude Era, mainRivalPromotion, World Championship Wrestling]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainRivalPromotion Context triple: [WWF Attitude Era, mainRivalPromotion, World Championship Wrestling]
-
A.
mainRivalState
Indicates that one state is considered the primary rival or chief adversary of another state.
-
B.
mainRivalAlliance
Indicates that one alliance is considered the primary or most significant rival of another alliance.
-
C.
primaryChallengers
Indicates that certain entities are the main or most significant opponents or competitors challenging another entity.
-
D.
rivalryFocus
Indicates a relationship in which one entity is the primary target or center of another entity’s competitive or adversarial rivalry.
-
E.
rivalOf
Indicates a relationship in which two entities compete against or oppose each other, often seeking advantage in the same domain or objective.
- 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_69f76dfbcdd881908c7b0b6bc502252b |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79da9f80c8190b0afd8509f28747b |
completed | May 3, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69f79617d40481909ba372f94209c08b |
completed | May 3, 2026, 6:38 p.m. |
| PDg | Predicate description generation | batch_69f79da8d8848190ab5ab1bdad95d58c |
completed | May 3, 2026, 7:10 p.m. |
Created at: May 3, 2026, 4:04 p.m.