Triple
T35854410
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Briscoe Brothers |
E1036456
|
entity |
| Predicate | wrestlingRegion |
P174634
|
FINISHED |
| Object | independent circuit |
—
|
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: independent circuit | Statement: [Briscoe Brothers, wrestlingRegion, independent circuit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wrestlingRegion Context triple: [Briscoe Brothers, wrestlingRegion, independent circuit]
-
A.
wrestledInRegion
chosen
Indicates that an entity participated in a wrestling activity or match that took place within a specified geographic region.
-
B.
notableTournamentRegion
Indicates that a tournament is notably associated with, recognized in, or significant within a particular geographic region.
-
C.
wrestlingPromotion
Indicates a relationship where an organization operates as a professional wrestling promotion, managing and presenting wrestling events or shows.
-
D.
wrestlingTerritoryPromoted
Indicates that a wrestling promotion or organization actively operated and promoted events within a specific wrestling territory.
-
E.
clubRegion
Indicates that a club is located in, associated with, or belongs to a particular geographic region.
- 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_69fba2877b248190a974eb092243c0c4 |
completed | May 6, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69fb8d06a1b48190a937aa410d159dfa |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 3, 2026, 4:06 p.m.