Triple
T27910745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kane |
E705920
|
entity |
| Predicate | storylineTagTeam |
P131760
|
FINISHED |
| Object | The Brothers of Destruction |
—
|
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: The Brothers of Destruction | Statement: [Kane, storylineTagTeam, The Brothers of Destruction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: storylineTagTeam Context triple: [Kane, storylineTagTeam, The Brothers of Destruction]
-
A.
featuredTeam
Indicates that a particular team is highlighted or given special prominence in a given context or presentation.
-
B.
fictionalTeam
Indicates that the related entities are members of, or otherwise associated with, the same fictional team within a narrative or imaginary context.
-
C.
teamAffiliationInStory
chosen
Indicates that, within the context of a particular story, one entity is affiliated with or belongs to a specific team.
-
D.
portraysFictionalTeam
Indicates that one entity depicts or represents a fictional team within a work or medium.
-
E.
stateTeam
Indicates that a team is officially associated with, represents, or belongs to a particular state.
- 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_69ef96b5aad08190be36a277c31e7004 |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f65876c52c8190bc889c7a67bd07f3 |
completed | May 2, 2026, 8:03 p.m. |
| PD | Predicate disambiguation | batch_69f6575d89788190aca478e4aea05a65 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 27, 2026, 6:49 p.m.