Triple
T35615629
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NXT Women’s Championship |
E1029156
|
entity |
| Predicate | introducedOnBrand |
P145378
|
FINISHED |
| Object | NXT |
—
|
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: NXT | Statement: [NXT Women’s Championship, introducedOnBrand, NXT]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedOnBrand Context triple: [NXT Women’s Championship, introducedOnBrand, NXT]
-
A.
introducedAsBrandFor
Indicates that one entity was presented or launched to the public specifically as the brand representing another entity.
-
B.
introducedUnderBrand
chosen
Indicates that one entity was launched, released, or brought to market using the branding or brand identity of another entity.
-
C.
introducedAsBrandBy
Indicates that one entity was presented or launched to the public or a market as a brand by another entity.
-
D.
introducedByProductLine
Indicates that one product line is responsible for introducing, launching, or bringing another product, feature, or offering into the market or portfolio.
-
E.
introducedAsProduct
Indicates that one entity is presented or launched in the role of a product in relation to another entity.
- 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_69f76e0709408190bbe322bf1707ef6b |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fe68a4b67881909ca1d9f276f922e0 |
completed | May 8, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69fe680234c88190b01f953987b74972 |
completed | May 8, 2026, 10:47 p.m. |
Created at: May 3, 2026, 4:05 p.m.