Triple
T35854449
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Briscoe Brothers |
E1036457
|
entity |
| Predicate | ROHWorldTagTeamTitleReigns |
P109119
|
FINISHED |
| Object | 13 |
—
|
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: 13 | Statement: [Briscoe Brothers, ROHWorldTagTeamTitleReigns, 13]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ROHWorldTagTeamTitleReigns Context triple: [Briscoe Brothers, ROHWorldTagTeamTitleReigns, 13]
-
A.
WorldTagTeamChampionshipReigns
chosen
Indicates the number or instances of times entities have held the World Tag Team Championship title.
-
B.
RingOfHonor
Indicates that an entity has been inducted into or recognized by a Ring of Honor, signifying formal commemoration or distinction within that context.
-
C.
twinTagTeam
Indicates a cooperative relationship where two twin entities act together as a coordinated team in performing an action or achieving a goal.
-
D.
wrestlingTitle
Indicates that an entity holds or is associated with a specific professional wrestling championship title.
-
E.
hasTagTeamDivision
Indicates that an entity participates in or is associated with a tag team division, typically involving teams of multiple members competing together.
- 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_69f76e1b4aa481909630373171eb5ec6 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7aa3883d48190b05e3d2da7a017ae |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8d435288190b30b1991fb003121 |
completed | May 3, 2026, 7:58 p.m. |
Created at: May 3, 2026, 4:06 p.m.