Triple
T38592449
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pulse Bomb |
E932484
|
entity |
| Predicate | effectRadius |
P1586
|
FINISHED |
| Object | small radius |
—
|
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: small radius | Statement: [Pulse Bomb, effectRadius, small radius]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: effectRadius Context triple: [Pulse Bomb, effectRadius, small radius]
-
A.
effectiveRadius_ly
Indicates the effective radius of something, measured in light-years, typically representing the distance from its center within which its influence or extent is considered significant.
-
B.
casualtyRadius
Indicates the distance from a central point within which people or objects are likely to be harmed or killed by an event or action.
-
C.
chargeRadius
Indicates the characteristic radial distance around an entity within which its electric charge or charge-related influence is considered effective.
-
D.
alsoEffectiveAtDistance
Indicates that the same effect or action remains valid or functional even when applied at a distance from its original or primary location.
-
E.
affectedArea
chosen
Indicates the specific region or extent over which an event, condition, or influence has an impact.
- 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fe68a4b67881909ca1d9f276f922e0 |
completed | May 8, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69fe680234c88190b01f953987b74972 |
completed | May 8, 2026, 10:47 p.m. |
Created at: May 3, 2026, 4:32 p.m.