Triple
T35810237
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phenomenal (WWE theme) |
E1035209
|
entity |
| Predicate | isEntranceThemeOf |
P184146
|
FINISHED |
| Object | AJ Styles |
—
|
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: AJ Styles | Statement: [Phenomenal (WWE theme), isEntranceThemeOf, AJ Styles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isEntranceThemeOf Context triple: [Phenomenal (WWE theme), isEntranceThemeOf, AJ Styles]
-
A.
themeParkAttraction
Indicates that something is an attraction or ride located within a theme park.
-
B.
locatedInThemeParkType
Indicates that an entity is situated within or belongs to a specific type or category of theme park.
-
C.
hasLandmarkAtEntrance
Indicates that a specific landmark is located at or directly adjacent to the entrance of something.
-
D.
themeParkAttractionAt
Indicates that a specific theme park attraction is located at or associated with a particular theme park or site.
-
E.
themeParkConnection
Indicates a relationship where two or more entities are connected through a theme park, such as by location, operation, partnership, or shared attractions.
- 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_69f76e1762408190b885a8456862e372 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7aaabb58c8190bf81673608ecfb6e |
completed | May 3, 2026, 8:06 p.m. |
| PD | Predicate disambiguation | batch_69f7a8d219f8819081dc4ce3c83ca0cb |
completed | May 3, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f7aa6795f481908940838ee7041ff5 |
completed | May 3, 2026, 8:04 p.m. |
Created at: May 3, 2026, 4:06 p.m.