Triple
T35806754
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hell’s Gate |
E1035120
|
entity |
| Predicate | requiresOpponentToTapOut |
P201021
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Hell’s Gate, requiresOpponentToTapOut, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresOpponentToTapOut Context triple: [Hell’s Gate, requiresOpponentToTapOut, true]
-
A.
requiresTapOff
Indicates that an action or process must be explicitly terminated, confirmed, or deactivated by performing a tap or similar user interaction.
-
B.
opponentRequirement
Indicates that a condition or set of conditions must be satisfied specifically by an opposing party or competitor.
-
C.
requiresWinningOnMultipleSurfaces
Indicates that achieving the objective depends on securing victories across more than one type of playing surface.
-
D.
pinfallOrSubmissionRequired
Indicates that achieving a victory in the context requires either a pinfall or a submission to be completed.
-
E.
requiresRefereeSignal
Indicates that the action or event can only proceed or be validated when a referee explicitly signals or authorizes it.
- 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_69ffc1550cb481908628e446d9b67f7b |
completed | May 9, 2026, 11:20 p.m. |
| PD | Predicate disambiguation | batch_69ffc10a74708190ae90e2c378791f70 |
completed | May 9, 2026, 11:19 p.m. |
| PDg | Predicate description generation | batch_69ffc15434c8819093aa3b33813613be |
completed | May 9, 2026, 11:20 p.m. |
Created at: May 3, 2026, 4:06 p.m.