Triple
T26346407
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Alliance |
E662786
|
entity |
| Predicate | onScreenOwner |
P132383
|
FINISHED |
| Object | Stephanie McMahon |
—
|
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: Stephanie McMahon | Statement: [The Alliance, onScreenOwner, Stephanie McMahon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: onScreenOwner Context triple: [The Alliance, onScreenOwner, Stephanie McMahon]
-
A.
hasOnScreenOwner
chosen
Indicates that an entity is owned or controlled by another entity that is explicitly shown or represented on screen.
-
B.
onScreenStatus
Indicates that an entity’s current presence or visibility state is being specified relative to a screen or display.
-
C.
onScreenLeader
Indicates that an entity serves as the primary or leading figure visibly presented on a screen in a given context or scene.
-
D.
onScreenDynamicWith
Indicates that two entities are simultaneously visible and interacting or changing together within the same on-screen context.
-
E.
hasOnscreenFunction
Indicates that an entity serves a particular role or performs a specific function when it appears on screen.
- 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_69ee81304194819092e20e0fae3aee07 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f60fa718188190a3f4d76db2cdf670 |
completed | May 2, 2026, 2:52 p.m. |
| PD | Predicate disambiguation | batch_69f602d2ec748190ae95154f34c7878f |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 26, 2026, 10:42 p.m.