Triple
T23917731
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sami Zayn |
E602126
|
entity |
| Predicate | competedInBrand |
P154357
|
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: [Sami Zayn, competedInBrand, NXT]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: competedInBrand Context triple: [Sami Zayn, competedInBrand, NXT]
-
A.
usesCompetitionBrand
Indicates that one entity makes use of a product, service, or brand that belongs to a competing company or organization.
-
B.
brandCompetedOn
Indicates that two brands have competed against each other in the same market, category, or competitive context.
-
C.
hasWorkedOnBrand
Indicates that an entity has performed work, tasks, or services related to a particular brand.
-
D.
usedBrand
Indicates that an entity has utilized, applied, or operated a particular brand in some context.
-
E.
competitiveBrandName
Indicates that one brand name is in a competitive relationship with another brand name in the same market or product space.
- F. None of above. chosen
Provenance (4 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_69e2953a187081908346a9f36e85fc98 |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f1cf153c6c819084aca5c13437fa3d |
completed | April 29, 2026, 9:27 a.m. |
| PD | Predicate disambiguation | batch_69f16151ebdc819086e9e1d7cc1f4f3c |
completed | April 29, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f16e348b548190b76e50f9b611f76d |
completed | April 29, 2026, 2:34 a.m. |
Created at: April 17, 2026, 8:40 p.m.