Triple
T35805504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Doom |
E1035091
|
entity |
| Predicate | unmaskedDuringRun |
P47249
|
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: [Doom, unmaskedDuringRun, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: unmaskedDuringRun Context triple: [Doom, unmaskedDuringRun, true]
-
A.
unmaskedPeriod
Indicates the duration during which an entity is not wearing or using a protective mask.
-
B.
exposedDuring
chosen
Indicates that something becomes visible, accessible, or subject to influence specifically within a given time period, event, or contextual interval.
-
C.
notHeldDuring
Indicates that a specified condition, event, or relationship does not occur or is not in effect throughout a given time interval or temporal context.
-
D.
suppressedDuring
Indicates that one event, action, or state is actively prevented, inhibited, or held back while another specified event, condition, or time period is occurring.
-
E.
runsDuring
Indicates that one event or process occurs within the temporal span of another event or process.
- 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_69f76e169bd081909f16cd8c9ee7870c |
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.