Triple
T35806772
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hell’s Gate |
E1035120
|
entity |
| Predicate | requiresRefereeStoppageIfNoTap |
P72050
|
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, requiresRefereeStoppageIfNoTap, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresRefereeStoppageIfNoTap Context triple: [Hell’s Gate, requiresRefereeStoppageIfNoTap, true]
-
A.
requiresOpponentToTapOut
Indicates that the action or outcome can only occur if an opposing participant submits or concedes by tapping out.
-
B.
requiresRingOfficials
Indicates that the event or activity cannot proceed or be valid unless designated ring officials are present or assigned.
-
C.
requiresRefereeSignal
chosen
Indicates that the action or event can only proceed or be validated when a referee explicitly signals or authorizes it.
-
D.
requiresTapOff
Indicates that an action or process must be explicitly terminated, confirmed, or deactivated by performing a tap or similar user interaction.
-
E.
isGoalLineStand
Indicates that an entity is positioned or formed as a defensive stand at the goal line, typically to prevent an opposing score.
- 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_69f76e1762408190b885a8456862e372 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ffc3f0b19c8190b5a749bc3cad21dd |
completed | May 9, 2026, 11:32 p.m. |
| PD | Predicate disambiguation | batch_69ffc1b882808190932b2d43ea5537c9 |
completed | May 9, 2026, 11:22 p.m. |
Created at: May 3, 2026, 4:06 p.m.