Triple
T12921023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gates of Hell |
E309119
|
entity |
| Predicate | isBurning |
P107024
|
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: [Gates of Hell, isBurning, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isBurning Context triple: [Gates of Hell, isBurning, true]
-
A.
burningSince
Indicates that an object or substance has been continuously burning from a specified starting time up to the present or another reference time.
-
B.
burnsWhen
Indicates that one entity causes another entity to ignite or combust when they come into contact or under specified conditions.
-
C.
burnsIn
Indicates that one entity undergoes combustion or is consumed by fire within or at the location of another entity.
-
D.
hasBurnUnit
Indicates that one entity (typically a medical facility) includes or is equipped with a specialized unit dedicated to the treatment and care of burn patients.
-
E.
burnedDuring
Indicates that one event, object, or process was actively burning or being consumed by fire during the time span of another specified event or interval.
- 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_69d7bdf92b588190acdf2a2291ac4590 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d971e7f6e881908c7bb12283898c80 |
completed | April 10, 2026, 9:55 p.m. |
| PD | Predicate disambiguation | batch_69d96fa9b7708190a9e9fa30f59ff580 |
completed | April 10, 2026, 9:46 p.m. |
| PDg | Predicate description generation | batch_69d9708a86bc8190bcdcf97e845bb413 |
completed | April 10, 2026, 9:50 p.m. |
Created at: April 9, 2026, 5:41 p.m.