Triple
T18962132
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Pretender |
E463937
|
entity |
| Predicate | hasExplosiveDynamics |
P76611
|
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: [The Pretender, hasExplosiveDynamics, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasExplosiveDynamics Context triple: [The Pretender, hasExplosiveDynamics, true]
-
A.
hasDynamics
Indicates that one entity exhibits or is characterized by specific dynamic behavior, changes, or variations over time in relation to another entity or context.
-
B.
hasFrequentExplosions
Indicates that the subject regularly experiences or produces explosions occurring at short or recurring intervals.
-
C.
explosivity
chosen
Indicates the degree to which something is prone to explode or cause an explosion under certain conditions.
-
D.
explosiveClass
Indicates the classification or category assigned to an explosive based on its type, properties, or regulatory class.
-
E.
moreExplosiveThan
Indicates that one entity has a greater degree of explosive power or volatility than another entity.
- 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_69d8dcffc278819086792a4ebfddfafa |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d5d368488190b0c7489335e5dd91 |
completed | April 20, 2026, 7:29 a.m. |
| PD | Predicate disambiguation | batch_69e4a2f437648190b85650dae8885d48 |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, noon