Triple
T29340965
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | thermal detonator |
E744034
|
entity |
| Predicate | inUniverseLegality |
P139339
|
FINISHED |
| Object | often illegal |
—
|
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: often illegal | Statement: [thermal detonator, inUniverseLegality, often illegal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inUniverseLegality Context triple: [thermal detonator, inUniverseLegality, often illegal]
-
A.
legalStatusInUniverse
chosen
Indicates the formal legal standing or classification an entity holds within a specified fictional or conceptual universe.
-
B.
inUniverseUseRestriction
Indicates that the use of something is restricted or limited within a specific fictional or defined universe or setting.
-
C.
inUniverseUse
Indicates that something is used or occurs within a particular fictional or conceptual universe, as opposed to in the real world or another setting.
-
D.
inUniverseRestriction
Indicates that something is limited, applicable, or valid only within a specific fictional or defined universe or continuity.
-
E.
inUniverseRarity
Indicates how rare or uncommon something is within the context of a specific fictional or defined universe.
- 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_69f09126cfcc8190899b16fbf3c2bf7b |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f6b2a65c7c8190ac40f1466ceadefc |
completed | May 3, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f6b14d7d508190bc7d4c89dfba4a32 |
completed | May 3, 2026, 2:22 a.m. |
Created at: April 28, 2026, 1:33 p.m.