Triple
T35806770
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hell’s Gate |
E1035120
|
entity |
| Predicate | hasRuleControversy |
P184904
|
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, hasRuleControversy, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRuleControversy Context triple: [Hell’s Gate, hasRuleControversy, yes]
-
A.
hasControversialAspect
Indicates that something includes an element, feature, or aspect that is disputed, debated, or likely to cause disagreement or public criticism.
-
B.
controversialBecause
Indicates that one entity is considered controversial specifically due to, or as a result of, its relationship with or association to another entity.
-
C.
hasCensorshipControversy
Indicates that an entity has been involved in disputes, criticism, or public debate related to censorship of its content or activities.
-
D.
roleInControversy
Indicates the specific part, involvement, or function an entity has within a particular controversy or disputed situation.
-
E.
controversialStatus
Indicates that the subject is associated with debate, dispute, or disagreement regarding its acceptance, validity, or appropriateness.
- 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_69f7b628b17c8190aa058c1a51852a27 |
completed | May 3, 2026, 8:55 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c06f5881908f0b98cad6796478 |
completed | May 3, 2026, 8:49 p.m. |
| PDg | Predicate description generation | batch_69f7b5cadd308190a864245a21b08f9a |
completed | May 3, 2026, 8:53 p.m. |
Created at: May 3, 2026, 4:06 p.m.