Triple
T26482216
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TNA World Heavyweight Championship |
E664717
|
entity |
| Predicate | isDefendedAt |
P161712
|
FINISHED |
| Object | Slammiversary |
—
|
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: Slammiversary | Statement: [TNA World Heavyweight Championship, isDefendedAt, Slammiversary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isDefendedAt Context triple: [TNA World Heavyweight Championship, isDefendedAt, Slammiversary]
-
A.
isDefendedAt
chosen
Indicates that a particular entity is protected or justified at a specific time, place, or context.
-
B.
isDefendedOn
Indicates that one entity provides protection, justification, or support for another entity in a specific context or situation.
-
C.
canBeDefendedIn
Indicates that something (such as a claim, action, or position) is capable of being justified or supported within a specified context, forum, or framework.
-
D.
defenderIn
Indicates that an entity serves as a defensive agent or protector within a specified context, situation, or domain.
-
E.
hasDefenderStrength
Indicates that an entity possesses a certain level or measure of defensive capability or protective power.
- 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_69ee883bc85481909885f92415cbce33 |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f621fcea1481909b6f8b3af1ee6820 |
completed | May 2, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69f620debeb48190b7db395fb86cf8d9 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 12:28 a.m.