Triple
T6530328
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WWE Tough Enough |
E152213
|
entity |
| Predicate | castingFocus |
P31
|
FINISHED |
| Object | independent wrestlers |
—
|
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 wrestlers | Statement: [WWE Tough Enough, castingFocus, independent wrestlers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: castingFocus Context triple: [WWE Tough Enough, castingFocus, independent wrestlers]
-
A.
cast
Indicates that an agent selects and assigns a person or thing to play a specific role or function in a production or context.
-
B.
castIn
Indicates that an actor or performer appears in a particular film, show, or production.
-
C.
theaterFocus
Indicates a relationship where an entity’s primary attention, activity, or specialization is centered on theater or theatrical performance.
-
D.
focusesOn
chosen
Indicates that one entity directs its attention, effort, or primary activity toward another entity or specific subject.
-
E.
castingType
Indicates the specific method or category of casting used to transform or represent one entity in terms of another.
- 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_69c688048ec8819093a47f7d332e12ec |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6adac53b0819097fece48a75cc48f |
completed | March 27, 2026, 4:17 p.m. |
| PD | Predicate disambiguation | batch_69c68abd9c7c819099e4fe8097cd1b28 |
completed | March 27, 2026, 1:48 p.m. |
Created at: March 27, 2026, 1:46 p.m.