Triple
T27929666
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lance Storm |
E707942
|
entity |
| Predicate | returnedForSpecialAppearances |
P116963
|
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: [Lance Storm, returnedForSpecialAppearances, WWE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: returnedForSpecialAppearances Context triple: [Lance Storm, returnedForSpecialAppearances, WWE]
-
A.
returnedFor
Indicates that an entity has been sent, given, or brought back in response to, or on behalf of, another entity or prior action.
-
B.
returnsInSpecial
chosen
Indicates that an entity returns to a designated special location, state, or context rather than a standard or default one.
-
C.
specialAppearance
Indicates that an entity makes a notable or exceptional appearance distinct from its usual or regular presence.
-
D.
appearsFor
Indicates that one entity is presented, shown, or made visible on behalf of, or in representation of, another entity.
-
E.
appearedWith
Indicates that two entities were present or participated together in the same context, event, or medium.
- 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_69ef96bbf2c48190a9d0e0291457aab6 |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f68805b4848190b75da14996d52a38 |
completed | May 2, 2026, 11:25 p.m. |
| PD | Predicate disambiguation | batch_69f68609c0b08190a8e1238a4d97c270 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 27, 2026, 7:02 p.m.