Triple
T27879127
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | X Division |
E705038
|
entity |
| Predicate | audienceAppeal |
P59531
|
FINISHED |
| Object | fans of action-oriented wrestling |
—
|
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: fans of action-oriented wrestling | Statement: [X Division, audienceAppeal, fans of action-oriented wrestling]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: audienceAppeal Context triple: [X Division, audienceAppeal, fans of action-oriented wrestling]
-
A.
audienceImpact
Indicates how an action, message, or event affects, influences, or resonates with its intended audience.
-
B.
audienceOrientation
Indicates how something is directed, tailored, or positioned with respect to a particular audience or group of recipients.
-
C.
audienceScale
Indicates the relative size or reach of the audience associated with an entity, event, or communication.
-
D.
attractsAudience
chosen
Indicates that an entity draws the interest or attention of people who choose to watch, listen to, or engage with it.
-
E.
relatesToAudience
Indicates a general relationship or relevance between something and a particular audience or group of recipients.
- 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_69ef84111bb4819084298f994b31c62f |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f63b317e048190963989b732b25b91 |
completed | May 2, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69f6370ea79c81909b761821ee0fa698 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 6:29 p.m.