Triple
T35806773
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hell’s Gate |
E1035120
|
entity |
| Predicate | isLegalInWWE |
P155172
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Hell’s Gate, isLegalInWWE, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLegalInWWE Context triple: [Hell’s Gate, isLegalInWWE, yes]
-
A.
legalIn
chosen
Indicates that an action, status, or entity is permitted or valid under the laws or regulations of a specified jurisdiction.
-
B.
legality
Indicates that an action, object, or situation conforms to, violates, or is evaluated in terms of formal laws or legal rules.
-
C.
hasLegalPosition
Indicates that an entity holds a specific legal role, status, or standing within a legal framework or proceeding.
-
D.
hasLegalStandingIn
Indicates that an entity possesses recognized legal status, rights, or capacity to act or be represented within a specified legal jurisdiction or context.
-
E.
hasLegalForceIn
Indicates that something (such as a law, regulation, or agreement) is legally valid, binding, and enforceable within a specified jurisdiction or context.
- 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_69f7aa699d68819081ed363931894ab3 |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8d219f8819081dc4ce3c83ca0cb |
completed | May 3, 2026, 7:58 p.m. |
Created at: May 3, 2026, 4:06 p.m.