Triple
T29991119
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spear (professional wrestling) |
E761880
|
entity |
| Predicate | promotionUsage |
P177157
|
FINISHED |
| Object | WWE |
—
|
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: WWE | Statement: [Spear (professional wrestling), promotionUsage, WWE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: promotionUsage Context triple: [Spear (professional wrestling), promotionUsage, WWE]
-
A.
campaignUsage
Indicates how a campaign is utilized or applied within a particular context or system.
-
B.
campaignUse
Indicates that one entity employs or leverages another as part of a campaign or organized promotional effort.
-
C.
usageAmong
Indicates how frequently or in what manner something is used within a particular group, context, or population.
-
D.
distributionUsage
Indicates how a distribution is intended to be used or applied within a given context.
-
E.
platformUsage
Indicates how an entity uses, engages with, or relies on a particular platform for its activities or services.
- 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_69f224695498819094a81037cad401e2 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6f85bfba48190aba95b40642a8ca7 |
completed | May 3, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f6f65fd1d08190b88e5e68ba268500 |
completed | May 3, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69f6f854486c81909396d944a55e03ab |
completed | May 3, 2026, 7:25 a.m. |
Created at: April 29, 2026, 6:38 p.m.